Add VersionMark support for tool version tracking in Build Notes PDF

[Copilot]

Pull Request

Description

Implements VersionMark integration to capture and report tool versions in Build Notes PDF, aligning with TemplateDotNetTool template (commit 25407e9ff).

Changes

Configuration

• Added VersionMark 0.1.0 to .config/dotnet-tools.json
• Created .versionmark.yaml defining version extraction patterns for 12 tools
• Special handling: SarifMark uses dotnet tool list --global (installed globally in CI, not locally)
• Updated .gitignore to exclude generated docs/buildnotes/versions.md

Workflow Updates (.github/workflows/build.yaml)

• quality-checks: Capture dotnet, git, versionmark early
• build (win/ubuntu): Capture dotnet, git, dotnet-sonarscanner, versionmark post-build
• integration-test: Sparse checkout .versionmark.yaml + .config/dotnet-tools.json, capture dotnet, git, versionmark
• build-docs: Consolidate all captures, publish to docs/buildnotes/versions.md with heading depth 1

PDF Integration

• Added docs/buildnotes/versions.md to docs/buildnotes/definition.yaml input files

Example Output

# Tool Versions

- **dotnet**: 10.0.102
- **git**: 2.52.0
- **node**: 24.13.0
- **npm**: 11.6.2
- **pandoc**: 3.9.0
- **weasyprint**: 68.1.0
- **sarifmark**: 1.0.0
- **sonarmark**: 1.1.0
- **reqstream**: 1.1.0
- **buildmark**: 0.2.0
- **versionmark**: 0.1.0

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code quality improvement

Related Issues

Pre-Submission Checklist

Before submitting this pull request, ensure you have completed the following:

Build and Test

• Code builds successfully: dotnet build --configuration Release
• All tests pass: dotnet test --configuration Release
• Code produces zero warnings

Code Quality

• Code formatting is correct: dotnet format --verify-no-changes
• New code has appropriate XML documentation comments
• Static analyzer warnings have been addressed

Quality Checks

Please run the following checks before submitting:

• Spell checker passes: cspell "**/*.{md,cs}"
• Markdown linter passes: markdownlint "**/*.md"
• YAML linter passes: yamllint '**/*.{yml,yaml}'
• Self-validation passes:
  dotnet run --project src/DemaConsulting.SarifMark --configuration Release --framework net10.0 --no-build -- --validate

Testing

• Added unit tests for new functionality
• Updated existing tests if behavior changed
• All tests follow the AAA (Arrange, Act, Assert) pattern
• Test coverage is maintained or improved

Documentation

• Updated README.md (if applicable)
• Updated ARCHITECTURE.md (if applicable)
• Added code examples for new features (if applicable)
• Updated requirements.yaml (if applicable)

Additional Notes

Workflow changes only affect CI/CD - no code changes to SarifMark tool itself. Build Notes PDF will now include tool versions section for audit trail and reproducibility.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.