[mrz1836]

What Changed

• Updated MAGE_X_VERSION from v1.24.0 to v1.24.1 in .github/env/10-mage-x.env
• Updated MAGE_X_BENCHSTAT_VERSION from v0.0.0-20260615155930-9e4b9ddef5b6 to v0.0.0-20260709024250-82a0b07e230d in .github/env/10-mage-x.env
• Updated GO_PRE_COMMIT_VERSION from v1.9.0 to v1.9.1 in .github/env/10-pre-commit.env
• Updated CodeQL GitHub Actions from commit 54f647b7e1bb85c95cddabcd46b0c578ec92bc1a (v4.36.3) to 99df26d4f13ea111d4ec1a7dddef6063f76b97e9 (v4.37.0) across codeql-analysis.yml and scorecard.yml
• Changed stale-check workflow schedule from Monday-Friday at 12:00 UTC (0 12 * * 1-5) to 1st of every month at 12:00 UTC (0 12 1 * *)
• Updated comment in stale-check.yml to reflect the new monthly schedule trigger

Why It Was Necessary

• Keep development tooling up-to-date with latest stable releases for bug fixes and improvements
• Update CodeQL to the latest version for improved security scanning capabilities
• Reduce frequency of stale issue checks from daily (weekdays) to monthly to decrease workflow runs and align with maintenance cadence

Testing Performed

• Verify environment variable syntax is correct and follows existing format conventions
• Validate workflow YAML syntax and cron expression format for the updated schedule
• Confirm CodeQL action references use valid commit SHA and version tags

Impact / Risk

• Breaking Change: None - these are dependency and workflow configuration updates
• Risk: Low - version bumps are minor/patch releases; workflow schedule change only affects automation frequency
• Performance: Reduced CI/CD resource usage due to less frequent stale-check workflow runs