Consolidate minor release ruleset and fix strict mode branch detection

[Alexander Holstrup (aholstrup1)]

What & why

Two related build-configuration changes for the strict mode / minor-release breaking-changes check:

1. Consolidate the minor-release ruleset. build/projects.json had the ruleSetPathMinorRelease property spread across several different files with inconsistent paths and casing, and ruleSetPath likewise pointed at multiple different files. This unifies them: every ruleSetPathMinorRelease now points to a new shared src/rulesets/baseminorrelease.ruleset.json, and every ruleSetPath points to src/rulesets/base.ruleset.json. The new ruleset includes base.ruleset.json plus the minor-release breaking-change rules (AS0077, AS0078, AS0102). PreCompileApp.ps1 is updated to resolve the new file name for the strict mode check.

2. Fix strict mode detection on release-branch CI/CD. On a push build against a release branch, Test-IsStrictModeEnabled resolved the branch via Get-CurrentBranch, which used git rev-parse --abbrev-ref HEAD. In GitHub Actions the checkout is a detached HEAD, so that returns the literal HEAD, which never matches ^releases/\d+\.\d+$. The result was strict mode being silently skipped on release branches (only PR builds worked, via GITHUB_BASE_REF). Get-CurrentBranch now returns GITHUB_REF_NAME when it is set, falling back to git only for local runs.

Centralizing the fix in Get-CurrentBranch also corrects the same latent detached-HEAD issue in the baseline-storage main branch check.

Linked work

Fixes #

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome

• Verified all 493 ruleSetPathMinorRelease and all 550 ruleSetPath entries in projects.json now resolve to a single path each, and that projects.json remains valid JSON.
• Parse-checked the edited PowerShell modules.
• Simulated branch resolution: push on releases/28.4 now resolves to releases/28.4 and matches the strict mode regex (previously HEAD, no match); PR into a release branch still works via GITHUB_BASE_REF; main and releases/NN.x correctly stay disabled (no numeric StrictMode tag).
• No AL tests added; changes are build-script/config only.

Risk & compatibility

• Behavior change: strict mode breaking-changes validation will now actually run on release-branch push builds where it was previously being skipped. This is the intended fix, but it may surface breaking-change analyzer errors that were not being reported before.
• The old src/rulesets/minorrelease.ruleset.json is now unreferenced. It was left in place in this PR; it can be removed in a follow-up if desired.

[github-actions]

Could not find a linked ADO work item. Please link one by using the pattern 'AB#' followed by the relevant work item number. You may use the 'Fixes' keyword to automatically resolve the work item when the pull request is merged. E.g. 'Fixes AB#1234'