3 AL/BC patterns: Insert/Delete trigger defaults on master data and declined Confirm in OnValidate (#209)

* Add trigger-default and declined-Confirm knowledge with review cues

Three Microsoft-layer articles with good/bad samples:
- error-handling/declined-confirm-must-abort-not-partially-apply
- data-modeling/delete-master-data-with-trigger
- data-modeling/master-data-must-be-inserted-with-trigger

Wire targeted worklist cues into al-error-handling-review and
al-data-modeling-review and register the samples in review-fixtures.json.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Tighten declined-confirm, delete and insert trigger articles after review

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

microsoft/knowledge/data-modeling/master-data-must-be-inserted-with-trigger.bad.al

@@ -0,0 +1,15 @@
+codeunit 50100 "Sample Customer Import"
+{
+    procedure CreateCustomer(ExternalName: Text[100]; ExternalCountry: Code[10]): Code[20]
+    var
+        Customer: Record Customer;
+    begin
+        Customer.Init();
+        Customer.Validate(Name, ExternalName);
+        Customer.Validate("Country/Region Code", ExternalCountry);
+        // RunTrigger defaults to false: OnInsert never runs, so "No." stays
+        // blank and no contact, salesperson, or timestamps are set.
+        Customer.Insert();
+        exit(Customer."No.");
+    end;
+}