Add 15 community knowledge articles from BC Code Intel ingest (#66)

* Add 15 community knowledge articles from BC Code Intel ingest

Ingests net-new /community knowledge from BC Code Intelligence, surviving
the admission test, gray-zone salvage, and dedup against the full corpus.

Domains: ui (6), error-handling (3), performance (2), upgrade (1),
appsource (1), security (1), telemetry (1). The two BC24 No. Series
migration drafts are merged into one article.

Adds good/bad AL samples for the clean-fit articles (error-handling,
performance, security, telemetry). UI and appsource remain knowledge-only.

Validator and knowledge-index checks pass (207 articles).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* Correct SetLoadFields JIT-load article to match MS docs

The draft claimed accessing an unlisted field "reloads the entire row"
per record. Microsoft's partial-records docs say otherwise: the platform
does an implicit Get that loads the missing field(s), and in a direct var
loop the first JIT updates the enumerator so later iterations do not
re-load. The genuine per-row penalty is the pass-by-value case, where the
copy's enumerator is not updated.

Rewrite the article around JIT loading and the by-value footgun, rename
the slug from ...full-reload to ...jit-load, and fix the good/bad samples
to demonstrate the by-value repetition accurately.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Jeremy Vyska <jeremy@sparebrained.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

community/knowledge/telemetry/default-telemetryscope-to-extensionpublisher.bad.al

@@ -0,0 +1,17 @@
+codeunit 50136 "Telemetry Bad Sample"
+{
+    procedure LogSyncDiagnostic(RecordsProcessed: Integer)
+    var
+        Dimensions: Dictionary of [Text, Text];
+    begin
+        Dimensions.Add('recordsProcessed', Format(RecordsProcessed));
+
+        // TelemetryScope::All pushes this internal diagnostic into every
+        // customer's Application Insights too, inflating their ingestion cost
+        // and burying their own signals in noise. ExtensionPublisher is the
+        // correct scope for publisher-only diagnostics.
+        Session.LogMessage(
+            'SYNC001', 'Nightly sync completed.', Verbosity::Normal,
+            DataClassification::SystemMetadata, TelemetryScope::All, Dimensions);
+    end;
+}