[Sync] Update project files from source repository (ac305ad)

[mrz1836]

What Changed

• Removed docs/*.md from .dockerignore to allow documentation files to be included in Docker builds
• Added new composite GitHub Action .github/actions/upload-artifact-resilient/action.yml with step-level retry logic (3 attempts with escalating delays of 10s, 30s) to handle transient infrastructure failures including non-retryable 403 errors
• Updated MAGE_X_VERSION from v1.12.1 to v1.12.2 in .github/env/10-mage-x.env
• Integrated the new resilient artifact upload action across 8 workflow files (code quality, benchmarks, coverage, completion statistics, security scans, fuzz testing, test matrix, test validation, and fork PR management)
• Added permissions: contents: read to all workflow jobs that use the new artifact upload action
• Replaced direct actions/upload-artifact@v4 calls with the new upload-artifact-resilient composite action across all workflows

Why It Was Necessary

• Documentation files need to be available in Docker containers for runtime reference or serving
• GitHub Actions artifact uploads were experiencing transient failures (403 errors from CDN/proxy intermediaries) that were not being handled by the built-in retry mechanism
• Centralizing artifact upload logic with resilient retry patterns improves CI/CD reliability and reduces manual intervention for infrastructure-related failures

Testing Performed

• Verified the composite action includes proper input validation and retry configuration (ACTIONS_UPLOAD_RETRY_COUNT=3, overwrite: true)
• Confirmed all workflow files correctly reference the new action with required inputs (artifact-name, artifact-path, retention-days)
• Validated that permissions are properly scoped with contents: read for artifact operations

Impact / Risk

• Low risk - The composite action wraps existing actions/upload-artifact@v4 functionality with additional resilience
• Improved reliability - Step-level retries with escalating delays should reduce transient failure rates in artifact uploads
• No breaking changes - All artifact uploads maintain the same retention policies and naming conventions