[Sync] Update project files from source repository (ec82cd5)

[mrz1836]

What Changed

• Updated goreleaser/goreleaser-action from commit e24998b8b67b290c2fa8b7c14fcfa7de2c5c9b8c (v7.1.0) to 1a80836c5c9d9e5755a25cb59ec6f45a3b5f41a8 (v7.2.1) in .github/actions/setup-goreleaser/action.yml
• Bumped GO_PRE_COMMIT_VERSION from v1.8.1 to v1.8.2 in .github/env/10-pre-commit.env
• Bumped GO_COVERAGE_VERSION from v1.3.8 to v1.3.9 in .github/env/10-coverage.env
• Updated MAGE_X_VERSION from v1.20.15 to v1.20.16 in .github/env/10-mage-x.env
• Updated MAGE_X_GORELEASER_VERSION from v2.15.3 to v2.15.4 in .github/env/10-mage-x.env

Why It Was Necessary

• Keeping tooling dependencies up-to-date ensures access to latest bug fixes and security patches
• Newer versions of these build and testing tools typically include performance improvements and stability enhancements
• Regular dependency updates reduce the risk of accumulated technical debt and potential compatibility issues

Testing Performed

• CI workflows will automatically validate the updated action and tool versions
• Pre-commit hooks and coverage tooling will be exercised in the normal development workflow
• GoReleaser action update will be validated during the next release build process

Impact / Risk

• Risk Level: Low - these are patch/minor version updates to development and CI tooling
• Breaking Changes: None expected - all updates appear to be backward-compatible maintenance releases
• CI Impact: Minimal - tools should function identically with potential minor performance improvements

[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