feat(FC0002): check casing of generic type arguments and subtyped object references

[Arthurvdv]

Closes #255

Problem

FC0002 raised no diagnostic for wrong casing inside List of [...] / Dictionary of [...] type declarations:

var
    MyList: List of [INTERFACE "IMYINTERFACE"];
    MyDict: Dictionary of [TEXT, INTERFACE "IMYINTERFACE"];

Two gaps in CasingMismatchIdentifier.WalkNode:

• GenericNamedDataTypeSyntax (SyntaxKind.GenericDataType) was never pushed onto the walk stack, so its TypeArguments were never visited — TEXT/INTERFACE inside the brackets went unchecked.
• The SubtypedDataTypeSyntax branch compared only the TypeName; the object name after Record/Codeunit/Interface/… was never compared against the declared symbol — anywhere, including top-level declarations.

Fix

• Push GenericDataType nodes onto the existing explicit stack (alongside EnumDataType/LabelDataType). ChildNodes() yields only the type-argument nodes, so the outer type name is not double-reported and nested generics recurse naturally.
• Collect IdentifierNameSyntax object references from subtyped data types and resolve them in a new batched ResolveObjectReferences pass — grouped by (TypeName, name) (separate from the identifiers list to avoid canonical-text cross-contamination with same-named variables), one GetSymbolInfo per group.
• New EnumProvider.SyntaxKind.GenericDataType member (nameof-based; the kind exists on the netstandard2.1 floor SDK).
• The existing CasingMismatchCodeFix (CanonicalText + QuoteIdentifierIfNeededWithReflection) applies to the new diagnostics unchanged — covered by new HasFix fixtures, including quote-dropping ("IMYINTERFACE" → IMyInterface) and re-quoting ("MY TABLE" → "My Table").
• Namespace-qualified references (Record MYPUBLISHER.MYEXTENSION.MYAPPDOMAIN.MYTABLE) are checked too, in a dedicated ResolveQualifiedObjectReferences pass: the object name is compared against symbol.Name, and each namespace part right-aligned against the declared namespace casing via GetContainingNamespaceQualifiedNameWithReflection (all-TFM safe).

Deliberately not checked: object references by numeric ID (Record 18).

Note: object-reference casing is now checked in all subtyped declarations (globals, locals, parameters, return values), not only inside generic brackets — fixing it brackets-only would have left an odd inconsistency. Severity stays Info.

Tests

• HasDiagnostic/NoDiagnostic fixtures GenericDataType.al, SubtypedObjectReference.al, and NamespacedObjectReference.al (regression-first: each HasDiagnostic case failed before its analyzer change). The Interface-in-generic fixtures are skipped below AL 14.0 (AL0408).
• HasFix/GenericTypeArgument, HasFix/QuotedObjectReference, and HasFix/QualifiedObjectReference.
• Full FormattingCop suite: 191/191 passing. CI builds of ALCops.Common and ALCops.FormattingCop green on netstandard2.1/net8.0/net10.0. dotnet format clean.

Companion docs PR in alcops.dev follows.

🤖 Generated with Claude Code