[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
• Updated MAGE_X_VERSION from v1.12.1 to v1.12.2 in .github/env/10-mage-x.env
• Updated all workflow files (fortress-code-quality.yml, fortress-coverage.yml, fortress-benchmarks.yml, fortress-completion-statistics.yml, fortress-test-fuzz.yml, fortress-security-scans.yml, fortress-test-matrix.yml, fortress-test-validation.yml, pull-request-management-fork.yml) to use the new upload-artifact-resilient composite action instead of direct actions/upload-artifact@v4 calls
• Added permissions: contents: read to workflows that previously had no permissions block

Why It Was Necessary

• GitHub Actions artifact uploads were experiencing transient infrastructure failures (403 errors from CDN/proxy intermediaries) that could not be recovered by the built-in retry logic
• Documentation files need to be available in Docker containers for runtime reference or distribution
• The new resilient upload action provides defense-in-depth against both 5xx server errors and non-retryable 403 errors through step-level retry with overwrite capabilities

Testing Performed

• The composite action implements configurable retry logic with overwrite: true on all attempts to handle partially-finalized artifacts
• All artifact upload operations across 9 workflow files have been migrated to use the standardized resilient upload pattern
• The action supports configurable inputs for artifact name, path, retention days, compression level, and continue-on-error behavior

Impact / Risk

• Risk: Low - The change introduces more resilient artifact handling without altering workflow behavior; failures that previously occurred will now be retried automatically
• Breaking Change: None - All workflows maintain their existing artifact upload configurations with added resilience
• Performance Impact: Minimal - Retry delays (10s, 30s) only trigger on failures; successful uploads remain unchanged

[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