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

[mrz1836]

What Changed

• Removed docs from .dockerignore, allowing documentation files to be included in Docker builds
• Added new composite action .github/actions/upload-artifact-resilient/action.yml with step-level retry logic (3 attempts with escalating delays of 10s, 30s) to handle transient GitHub infrastructure failures including non-retryable 403 errors
• Created three new environment files: .github/env/10-coverage.env, .github/env/10-mage-x.env, and .github/env/10-pre-commit.env
• Updated MAGE_X_VERSION from v1.12.1 to v1.12.2 in .github/env/10-mage-x.env
• Modified multiple workflow files (fortress-code-quality.yml, fortress-benchmarks.yml, fortress-completion-statistics.yml, fortress-coverage.yml, fortress-security-scans.yml, fortress-test-fuzz.yml, fortress-test-matrix.yml, fortress-test-validation.yml, pull-request-management-fork.yml) to add permissions: contents: read, load environment variables from the new env files, and replace direct actions/upload-artifact@v4 calls with the new upload-artifact-resilient action
• Added configurable inputs to the resilient upload action including artifact-name, artifact-path, retention-days, if-no-files-found, and compression-level

Why It Was Necessary

• Centralized artifact upload logic to handle transient GitHub Actions infrastructure failures that were causing workflow failures due to non-retryable 403 errors during artifact finalization
• Improved workflow reliability by implementing step-level retry mechanisms with overwrite capabilities to recover from partially-finalized artifacts
• Standardized environment variable management by extracting configuration into dedicated env files for better maintainability and consistency across workflows
• Enhanced security posture by adding explicit contents: read permissions to workflows following principle of least privilege

Testing Performed

• Validated that the new composite action properly implements retry logic with configurable delays and overwrite behavior
• Verified all workflow files correctly reference the new environment files and resilient upload action
• Confirmed artifact upload paths and names are preserved across all workflows using the new action
• Tested that workflows maintain backward compatibility with existing artifact retention policies and compression settings

Impact / Risk

• Low Risk: Changes primarily improve reliability and maintainability without altering core workflow functionality
• Breaking Change: None - artifact uploads maintain same external behavior with added resilience
• Performance: Potential slight increase in workflow duration during retry scenarios, but improved overall success rate for artifact uploads
• Developer Experience: Improved workflow stability reduces false failures and manual reruns, while centralized configuration simplifies future updates