[Sync] Update project files from source repository (9def984)

[mrz1836]

What Changed

• Updated GO_PRE_COMMIT_VERSION from v1.7.0 to v1.8.0 in .github/env/10-pre-commit.env
• Updated GO_PRE_COMMIT_GOLANGCI_LINT_VERSION from v2.11.1 to v2.11.2 in .github/env/10-pre-commit.env
• Updated MAGE_X_VERSION from v1.20.7 to v1.20.8 in .github/env/10-mage-x.env
• Updated MAGE_X_GOLANGCI_LINT_VERSION from v2.11.1 to v2.11.2 in .github/env/10-mage-x.env
• Updated MAGE_X_GORELEASER_VERSION from v2.14.1 to v2.14.2 in .github/env/10-mage-x.env
• Updated MAGE_X_MAGE_VERSION from v1.15.0 to v1.16.0 in .github/env/10-mage-x.env
• Updated GoFortress workflow version comment from 1.7.1 (released 2026-02-13) to 1.7.2 (released 2026-03-09) in .github/workflows/fortress.yml

Why It Was Necessary

• Keeping tooling dependencies up to date ensures access to latest bug fixes, security patches, and performance improvements
• Maintaining consistent versions of golangci-lint across pre-commit and mage-x environments prevents conflicts and ensures reproducible builds
• Regular updates to CI/CD tooling (GoReleaser, Mage) improve build reliability and workflow execution

Testing Performed

• Verify that CI/CD workflows execute successfully with updated tool versions
• Confirm pre-commit hooks run without errors using the new go-pre-commit version
• Validate that mage-x tasks complete successfully with updated dependencies

Impact / Risk

• Breaking Change: None - these are patch/minor version updates to tooling
• Risk: Low - updates are incremental and limited to development/CI tooling versions
• Performance: Potential improvements from tool updates, no expected degradation
• Migration: No action required - environment files control version resolution automatically