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

[mrz1836]

What Changed

• Updated actions/cache and actions/cache/restore and actions/cache/save from commit hash 0400d5f644dc74513175e3cd8d07132dd4860809 (v4.2.4) to 668228422ae6a00e4ad889ee87cd7109ec5666a7 (v5.0.4) across multiple workflow files and action definitions
• Updated actions/setup-go from commit hash d35c59abb061a4a6fb18e82ac0862c26744d6ab5 (v5.5.0) to a newer version in .github/actions/setup-go-with-cache/action.yml
• Removed comments stating "Uses actions/cache@v4 which handles both restore and save" from two cache step sections in the setup-go-with-cache action
• Applied these GitHub Actions dependency updates across 19 files including cache-redis-image, setup-go-with-cache, setup-benchstat, setup-goreleaser, setup-magex, upload-artifact-resilient, setup-mage, upload-statistics, warm-cache actions, and various workflow files

Why It Was Necessary

• Upgrading to actions/cache v5.0.4 provides security updates, bug fixes, and performance improvements from the upstream GitHub Actions repository
• Using pinned commit hashes alongside version tags ensures supply chain security while maintaining reproducible builds
• Removing outdated comments reduces maintenance burden and prevents documentation drift as the action APIs evolve

Testing Performed

• Verified all modified workflow files and actions maintain valid YAML syntax
• Confirmed commit hashes correspond to the documented version tags (v5.0.4 for actions/cache family)
• Validated that the cache action invocations retain the same input parameters and conditional logic after the version update
• Ensured no breaking changes in the v4 to v5 upgrade path for actions/cache affect existing cache restore/save operations

Impact / Risk

• Low risk: GitHub Actions cache v5.0.4 maintains backward compatibility with v4.2.4 usage patterns
• CI/CD stability: Existing caches may be invalidated or recreated depending on the internal changes in the cache action, potentially causing temporary cache misses
• No breaking changes: All workflow syntax, input parameters, and output variables remain unchanged in the updated action versions
• Security improvement: Using the latest action versions reduces exposure to known vulnerabilities in older releases

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