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

[mrz1836]

What Changed

• Added new composite action .github/actions/upload-artifact-resilient/action.yml that provides step-level retry logic (3 attempts with escalating delays of 10s, 30s) for artifact uploads to handle transient GitHub infrastructure failures including non-retryable 403 errors
• Modified 12 workflow files to use the new upload-artifact-resilient composite action instead of direct actions/upload-artifact calls
• Added configurable inputs to the composite action including artifact-name, artifact-path, retention-days, if-no-files-found, compression-level, and continue-on-error
• Configured all upload attempts with overwrite: true and ACTIONS_UPLOAD_RETRY_COUNT=3 for defense-in-depth against infrastructure failures

Why It Was Necessary

• Transient GitHub infrastructure failures (including CDN/proxy 403 errors during artifact finalization) were causing workflow failures that required manual reruns
• The native actions/upload-artifact retry mechanism doesn't handle certain non-retryable errors at the step level, requiring a wrapper with explicit retry logic
• Centralizing artifact upload resilience logic in a composite action provides consistent error handling across all workflows and reduces maintenance burden

Testing Performed

• Verified the composite action syntax follows GitHub Actions composite action schema with proper input definitions and step configurations
• Confirmed retry logic uses escalating delays (10s, 30s) between attempts to handle transient infrastructure issues
• Validated that all 12 workflow files correctly reference the new composite action with appropriate input parameters

Impact / Risk

• Risk Level: Low - The change wraps existing actions/upload-artifact@v4 functionality with additional retry logic, maintaining backward compatibility
• Failure Handling: Non-critical artifacts have continue-on-error: true by default, preventing workflow failures while still logging upload issues
• Performance: Introduces up to 40 seconds of additional delay per artifact upload in worst-case scenarios (3 attempts with escalating delays), but only when uploads fail

[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