Add CMFRT coding standards documentation and examples

- Introduced guidelines for "one codeunit one global function" architecture to enforce single responsibility in AL code.
- Added best practices and anti-patterns for adding parameters via overloads to maintain backward compatibility.
- Documented the importance of never deleting members in AL and always marking them as obsolete.
- Established the requirement for OnBefore and OnAfter integration events for global procedures to enhance extensibility.
- Defined naming conventions for CMFRT objects, including prefixes and object ID ranges to avoid conflicts.
- Implemented patterns for case statements to ensure all cases are handled, including the necessity of an else clause.
- Introduced the interface injection pattern to allow pluggable operations in table-level code.
- Recommended using Confirm Management for user confirmations to improve testability.
- Established a three-permission set pattern for security to ensure proper access control.
- Created a review skill for CMFRT AL standards to automate compliance checks against established guidelines.

custom/knowledge/patterns/cmfrt-interface-injection.bad.al

@@ -0,0 +1,12 @@
+// Monolithic entry-point: the implementation is embedded, there is no interface,
+// and there is no OnBefore event. Dependent extensions cannot override the
+// calculation without an AL override hack.
+table 2045090 "CMFRT MS Measure State"
+{
+    procedure CalcTotals()
+    begin
+        // All calculation logic is hard-coded here.
+        Rec."Total Amount" := Rec."Line Amount" + Rec."Tax Amount";
+        Rec.Modify();
+    end;
+}