[Sync] Update project files from source repository (3218cb1)

[mrz1836]

What Changed

• Updated MAGE_X_VERSION from v1.15.5 to v1.17.4 in .github/.env.base
• Updated MAGE_X_GORELEASER_VERSION from v2.13.2 to v2.13.3
• Updated MAGE_X_BENCHSTAT_VERSION from v0.0.0-20251208221838-04cf7a2dca90 to v0.0.0-20260112171951-5abaabe9f1bd
• Added new configuration variable MAGE_X_MAGE_VERSION=v1.15.0
• Updated GO_PRE_COMMIT_VERSION from v1.4.6 to v1.5.1
• Created new composite action .github/actions/setup-mage/action.yml for installing and caching the mage binary
• Modified .github/workflows/fortress-test-matrix.yml (content changes not shown in truncated diff)

Why It Was Necessary

• Updating MAGE-X and its tool dependencies ensures access to latest features, bug fixes, and security patches
• The new setup-mage composite action provides efficient binary caching by OS and version, improving workflow performance
• Standardizing mage installation across workflows through a reusable action reduces duplication and maintenance overhead

Testing Performed

• Verify that workflows using the new setup-mage action successfully install and cache the mage binary
• Confirm that updated tool versions (goreleaser, benchstat) execute without compatibility issues
• Test cache hit/miss scenarios to validate the caching mechanism works correctly across different OS runners

Impact / Risk

• Low Risk: Version updates are incremental and within the same major versions for most tools
• CI Performance: Introduction of binary caching should reduce workflow execution time on cache hits
• Compatibility: Updated MAGE-X version (v1.15.5 → v1.17.4) spans multiple minor versions; monitor for any breaking changes in workflow behavior

[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!