Standardize build-docs shell to bash for SarifMark consistency

[Copilot]

Pull Request

Description

Aligns build-docs job with SarifMark's workflow patterns. All shell-dependent steps now use bash explicitly instead of mixed PowerShell, ensuring consistent cross-platform behavior and maintainability between sister projects.

Changes:

• Shell specifications: pwsh → bash for install, generate, and display steps
• Command syntax: PowerShell backticks → bash backslashes, $env:SONAR_TOKEN → $SONAR_TOKEN
• Report display: Get-Content → cat
• Tool invocation: Correctly uses dotnet sarifmark (local tool via dotnet-tools.json) and sonarmark (globally installed)

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

N/A

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}'

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-only change. No code or test modifications required. YAML validated with yamllint. CodeQL security scan passed.

Original prompt

Please review the build.yaml from https://github.com/demaconsulting/SarifMark and make this projects build more consistent - especially around the build-docs with regards to shell specifications and how the reports are printed.

---

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

[Malcolmnixon]

The sarifmark tool still needs to be run using 'dotnet sarifmark' as it's installed locally via the dotnet-tools.json file in this project. This isn't needed for the 'sonarmark' tool later as that one is installed globally in this project.

[Copilot]

Fixed in 7ee3bfd. Changed to dotnet sarifmark since it's installed locally via dotnet-tools.json, while sonarmark remains directly callable as it's installed globally.