What Changed

• Added github-token input parameter to .github/actions/setup-go-with-cache/action.yml and .github/actions/warm-cache/action.yml for private module authentication
• Added new conditional step "🔐 Configure private module authentication" in setup-go-with-cache action that runs only when both github-token and GOPRIVATE environment variable are set
• The authentication step configures git to use token-based HTTPS authentication for GitHub URLs and sets GONOSUMDB to match GOPRIVATE if not already set
• Added github-token: ${{ secrets.GITHUB_TOKEN }} parameter to setup-go-with-cache and warm-cache action calls across multiple workflow files (fortress-code-quality.yml, fortress-benchmarks.yml, fortress-coverage.yml, fortress-release.yml, fortress-pre-commit.yml, fortress-test-fuzz.yml, fortress-test-matrix.yml, fortress-setup-config.yml, fortress-security-scans.yml, fortress-warm-cache.yml, fortress-test-suite.yml, fortress.yml)

Why It Was Necessary

• Enable support for private Go modules that require authentication to access
• Provide a standardized mechanism across all workflows to handle private dependencies when GOPRIVATE is configured
• Allow the Go toolchain to authenticate with private GitHub repositories without requiring manual configuration in each workflow

Testing Performed

• Verify workflows continue to function correctly with the new github-token parameter added
• Test that private module authentication step is skipped when GOPRIVATE is not set (existing behavior unchanged)
• Validate that git configuration is properly set when both token and GOPRIVATE are provided

Impact / Risk

• Low Risk: Changes are backward compatible - the authentication step only runs conditionally when both token and GOPRIVATE are present
• No Breaking Changes: Existing workflows without private modules continue to work unchanged
• Security Consideration: Token is passed as environment variable and used only for git configuration, following GitHub's recommended authentication pattern