[Sync] Update project files from source repository (58a7526)

[mrz1836]

What Changed

• Updated .dockerignore to include !dist/linux-amd64/ and !dist/linux-arm64/ alongside the existing !dist/linux/ exclusion
• Removed maintainer comment (# Maintainer: @mrz1836) from .github/.yamlfmt configuration file
• Added exclusion for test fixture file .github/ci-tester/fixtures/workflow-invalid/.github/workflows/invalid.yml in yamlfmt configuration
• Updated .github/CODEOWNERS to remove ownership entries for .github/.env.base and .github/.env.custom, and changed .github/.gitleaks.toml to .gitleaksignore
• Modified MAGE_X_VERSION from v1.12.1 to v1.12.2 across multiple workflow and action files (fortress-completion-finalize.yml, fortress-completion-statistics.yml, fortress-completion-tests.yml, fortress-test-magex.yml, fortress-test-validation.yml, pull-request-management-fork.yml, setup-goreleaser/action.yml, setup-magex/action.yml, validate-test-results/action.yml)
• Added permissions: contents: read to multiple workflow files (fortress-code-quality.yml, fortress-security-scans.yml, fortress-coverage.yml, codeql-analysis.yml, fortress-benchmarks.yml, auto-merge-on-approval.yml, fortress-pre-commit.yml, fortress-completion-report.yml, dependabot-auto-merge.yml, fortress-release.yml, fortress-setup-config.yml, fortress-test-matrix.yml, fortress-warm-cache.yml, fortress-test-fuzz.yml, fortress.yml, fortress-test-suite.yml, scorecard.yml, stale-check.yml, pull-request-management.yml, sync-labels.yml)

Why It Was Necessary

• Multi-architecture Docker builds require separate linux-amd64 and linux-arm64 directories to be preserved during build context
• Mage-x tool upgraded to version 1.12.2 to incorporate latest features and bug fixes
• GitHub Actions security best practices require explicit permissions declarations, implementing principle of least privilege
• Test fixture exclusion prevents yamlfmt from attempting to format intentionally malformed YAML files used for validation testing

Testing Performed

• Verified Docker builds can access architecture-specific distribution directories
• Confirmed yamlfmt no longer processes the excluded test fixture file
• Validated all GitHub Actions workflows continue to function with explicit permissions
• Tested that mage-x v1.12.2 executes successfully across all workflows and composite actions

Impact / Risk

• Breaking Change: None - changes are additive or internal configuration updates
• Performance: No performance impact expected from permission declarations or version updates
• Risk: Low - explicit permissions may prevent workflows from accessing resources they previously had implicit access to, though all modified workflows appear to only require read access to contents
• Migration: None required - workflows will automatically use updated configurations on next run

[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