[Sync] Update project files from source repository (5c903c5)

[mrz1836]

What Changed

• Updated MAGE_X_VERSION from v1.20.1 to v1.20.4
• Updated MAGE_X_GOLANGCI_LINT_VERSION from v2.8.0 to v2.9.0
• Updated MAGE_X_STATICCHECK_VERSION from 2025.1.1 to 2026.1
• Updated MAGE_X_BENCHSTAT_VERSION from v0.0.0-20260112171951-5abaabe9f1bd to v0.0.0-20260211190930-8161c38c6cdc
• Added new fuzz test configuration section with MAGE_X_FUZZ_WARMUP_TIMEOUT set to 5m and commented-out variables for MAGE_X_FUZZ_BASELINE_BUFFER, MAGE_X_FUZZ_BASELINE_OVERHEAD_PER_SEED, and MAGE_X_FUZZ_MIN_TIMEOUT

Why It Was Necessary

• Upgrade to latest MAGE-X version (v1.20.4) to incorporate bug fixes and improvements
• Update linting and static analysis tools to their latest versions for improved code quality checks
• Add fuzz test configuration to support warming the Go build cache before running fuzz tests, preventing timeouts in projects with large dependency trees

Testing Performed

• Verify MAGE-X v1.20.4 runs successfully with updated tool versions
• Confirm golangci-lint v2.9.0 and staticcheck 2026.1 execute without errors
• Test fuzz test warmup behavior with the new MAGE_X_FUZZ_WARMUP_TIMEOUT=5m setting to ensure build cache warming prevents first-test timeouts

Impact / Risk

• Low Risk: Version updates are incremental and tools are well-tested in their respective upstream projects
• Developer Experience: Fuzz test warmup configuration should improve CI reliability by preventing timeout issues in the first fuzz test per package
• No Breaking Changes: All changes are to build tooling versions and configuration; no application code or APIs are affected

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