[Sync] Update project files from source repository (2f986b0)

[mrz1836]

What Changed

• Modified .github/actions/parse-env/action.yml to move the ENV_JSON input from an inline shell variable to the env: context for improved security
• Added a new github-token input parameter to .github/actions/setup-go-with-cache/action.yml for private module authentication (optional, defaults to empty string)
• Added a new conditional step "🔐 Configure private module authentication" in setup-go-with-cache that configures git authentication for private Go modules when both github-token and GOPRIVATE are set
• Updated multiple workflow files to pass github-token: ${{ secrets.GITHUB_TOKEN }} to the setup-go-with-cache action
• Modified environment variable files including 00-core.env, 10-mage-x.env, and 10-pre-commit.env (specific changes to variables like MAGE_X_VERSION from v1.12.1 to v1.12.2)
• Added or updated permissions: blocks in various workflow files to explicitly set contents: read

Why It Was Necessary

• Moving ENV_JSON to the environment context prevents potential injection attacks by avoiding direct interpolation of user input into shell scripts
• Private Go module support enables workflows to access dependencies hosted in private repositories without manual git configuration
• Explicit permission declarations follow GitHub Actions security best practices by implementing least-privilege access
• Version updates ensure workflows use the latest stable releases of tooling dependencies

Testing Performed

• Validated that environment variable parsing continues to work with the new env: context approach
• Verified that private module authentication only triggers when both GOPRIVATE is set and a token is provided
• Confirmed existing workflows continue to function with the new permission blocks and token passing
• Tested that GONOSUMDB is automatically set to match GOPRIVATE when not explicitly defined

Impact / Risk

• Breaking Change: None - all changes are backward compatible with optional parameters and conditional logic
• Security Improvement: Reduced injection attack surface by moving input handling to environment context, explicit permissions limit workflow scope
• Risk: Low - private module authentication is opt-in and only activates when explicitly configured with both GOPRIVATE and a token