feat: support commit SHA placeholders in branch labels

[arturcic]

Description

Branch labels such as label: 'ci.{ShortSha}' currently fail with an unknown-placeholder error. Add {Sha} and {ShortSha} using the commit being versioned, so these templates participate in version calculation under calculation.branches.<branch>.label.

Pass the calculation commit through version-search strategies and recursive mainline traversal. Reuse the existing seven-character short-SHA operation. Named regex captures retain precedence, including empty captures, and existing formatting, fallbacks, sanitization, and missing-placeholder errors remain unchanged.

Update the configuration reference and generated v7 schema. The same templates work through explicit v6 compatibility mode and configuration migration.

Related Issue

Resolves #3035

Motivation and Context

Allow commit hashes in calculated prerelease labels while preserving existing regex-based configurations. The new built-ins are limited to Sha and ShortSha; prerelease numbering continues to follow the selected deployment mode.

How Has This Been Tested?

Local validation on macOS with .NET 10:

• Full core suite: 36,269 passed.
• Full configuration suite: 198 passed.
• CLI configuration integration suite: 25 passed.
• History regressions cover both managed and LibGit2Sharp backends, successive commits, explicit historical commits, nested merges, and tagged-current behavior.
• Temporarily removing the SHA inputs caused six new placeholder cases to fail; restoring them returned the configuration suite to green.
• Full solution build: zero warnings/errors. Formatting and diff checks passed.
• Repeated schema/reference generation produced identical files.

Checklist

• Code follows the project style.
• Documentation and generated schema updated.
• Regression tests added.
• Relevant test suites passed.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

🔵 Needs a closer look

It changes core version calculation pathways (including mainline traversal) by threading commit context broadly, so a final human review should validate the behavioral impact despite strong test coverage.

Review details

• Files reviewed: 30/30 changed files
• Comments generated: 1
• Review effort level: Lite

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[asbjornu]

LGTM, just got a few questions and comments.

[Copilot]

🔵 Needs a closer look

It makes broad, cross-cutting changes in core version-calculation paths (strategies + recursive mainline traversal), and should receive final human sign-off despite strong test coverage updates.

Review details

• Files reviewed: 30/30 changed files
• Comments generated: 0 new
• Review effort level: Lite

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[arturcic]

Thanks! Updated the wording and regenerated the schema. Both tests now deserialize into GitVersionConfiguration; the migration test retains explicit YAML structure checks.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.5% Duplication on New Code

See analysis details on SonarQube Cloud

[mergify]

Thank you @arturcic for your contribution!