[Sync] Update project files from source repository (425438b)

[mrz1836]

What Changed

• Updated actions/cache from v5.0.2 (commit 8b402f5) to v5.0.3 (commit cdf6c1f) across multiple workflow files:
  • fortress-code-quality.yml: Updated 3 cache action instances (golangci-lint binary cache, build cache, and analysis cache)
  • fortress-coverage.yml: Updated 2 cache action instances (Go build cache and coverage cache)
  • fortress-release.yml: Updated Go build cache action
  • fortress-pre-commit.yml: Updated Go build cache action
  • fortress-security-scans.yml: Updated 2 cache action instances (Go build cache and Trivy cache)
  • fortress-test-matrix.yml: Updated Go build cache action
  • fortress-setup-config.yml: Updated cache action
  • fortress.yml: Updated cache action
• Enhanced error message in fortress-benchmarks.yml from "::error::Benchmark execution failed or contained errors" to "::error title=Benchmark Failed::Benchmark execution failed or contained errors (panic, fatal, or timeout) - see job summary for details"
• Improved input parsing in fortress-completion-finalize.yml to use base64 encoding and heredoc syntax for safely handling multiline values (e.g., env-json), with hyphen-to-underscore conversion for GitHub Actions expression compatibility

Why It Was Necessary

• Updating actions/cache to v5.0.3 brings in the latest bug fixes and improvements from the upstream GitHub action
• The enhanced benchmark error message provides more specific context about failure types (panic, fatal, timeout) and directs users to the job summary, improving debugging experience
• The input parsing improvement prevents issues when handling multiline workflow input values that could break with simple delimiter-based parsing

Testing Performed

• Verify all workflow files with updated cache actions maintain correct syntax and reference structure
• Confirm benchmark workflow properly displays enhanced error message with title annotation when benchmarks fail
• Test completion finalization workflow with multiline input values (particularly env-json) to ensure base64 encoding handles them correctly

Impact / Risk

• Breaking Change: None - these are backward-compatible updates to workflow dependencies and error messaging
• Risk: Low - cache action update is a minor version increment; input parsing change is internal to workflow execution and maintains the same functional behavior
• Performance: No performance impact expected; cache action updates may improve caching reliability

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[mrz1836]

LGTM!