Add data-modeling and appsource knowledge articles (MICROSOFT layer)

Author 7 remedial BCQuality knowledge articles plus good/bad AL samples
(21 files) covering AL master-table and data-model design:

- data-modeling: master No. from number series in OnInsert; use codeunit
  "No. Series" not obsolete NoSeriesManagement; setup table is a singleton;
  set Last Date Modified in OnModify and OnRename; enforce Blocked in
  referencing code not in the master.
- style: ApplicationArea required on page controls (AS0062).
- appsource: object affixes prevent collisions (AS0011).

Clean-room authored from own BC knowledge; specifics verified against public
sources only (learn.microsoft.com, microsoft/BCApps). Introduces two new
domains (data-modeling, appsource).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

microsoft/knowledge/data-modeling/master-table-no-from-number-series-in-oninsert.bad.al

@@ -0,0 +1,31 @@
+table 50361 "Loyalty Member"
+{
+    Caption = 'Loyalty Member';
+    DataClassification = CustomerContent;
+
+    fields
+    {
+        // Anti-pattern: an autoincrement Integer surrogate used as the business key.
+        field(1; "Entry No."; Integer)
+        {
+            Caption = 'Entry No.';
+            AutoIncrement = true;
+        }
+        field(10; Name; Text[100])
+        {
+            Caption = 'Name';
+        }
+    }
+
+    keys
+    {
+        key(PK; "Entry No.")
+        {
+            Clustered = true;
+        }
+    }
+
+    // No OnInsert, no number series, no "No." code, and no "No. Series" field.
+    // Records get an opaque integer users never see and cannot quote on the phone,
+    // and the master is cut off from BC's standard numbering and manual-entry flow.
+}