Add configurable projectScanDepth for project discovery

[mazhelez]

Problem

The \GetProjectsFromRepository\ function in \AL-Go-Helper.ps1\ uses a hardcoded -Depth 2\ when auto-discovering AL-Go projects (scanning for .AL-Go/settings.json\ directories). This means repositories that nest their projects deeper than 2 levels from the root cannot use automatic project discovery.

For example, a repository with projects at \�ng/AL-Go/projects/MyProject/.AL-Go/settings.json\ (depth 3) will not find any projects, leading to a strict mode error:
\
The variable '' cannot be retrieved because it has not been set.
\\

This happens because when no projects are found, the \if ()\ block is skipped, leaving \\ uninitialized, but line 231 still tries to access \.projectDependencies.

Fix

1. *New setting: \projectScanDepth* (default: 2) — Controls the -Depth\ parameter for automatic project discovery. Repositories can increase this in .github/AL-Go-Settings.json:
   \\json
   { "projectScanDepth": 4 }
   \\

2. Defensive initialization — \\ is now initialized with safe defaults before the \if ()\ guard, preventing strict mode errors when no projects are discovered.

3. Schema update — Added \projectScanDepth\ to \settings.schema.json\ for IntelliSense support.

Files Changed

• \Actions/.Modules/ReadSettings.psm1\ — Added default setting
• \Actions/.Modules/settings.schema.json\ — Added schema definition
• \Actions/AL-Go-Helper.ps1\ — Added -scanDepth\ parameter to \GetProjectsFromRepository; updated internal caller
• \Actions/CheckForUpdates/CheckForUpdates.ps1\ — Pass \scanDepth\
• \Actions/DetermineProjectsToBuild/DetermineProjectsToBuild.psm1\ — Pass \scanDepth; initialize \\
• \Actions/IncrementVersionNumber/IncrementVersionNumber.ps1\ — Pass \scanDepth\

Backward Compatibility

The default value of 2 preserves existing behavior. Only repositories that explicitly set \projectScanDepth\ to a higher value will see different discovery behavior.