Investigate workflow job failing on main: build (developmentDebug, false)

[github-actions]

🚨 Failure Summary 🚨:

• 📋 Job Name: build (developmentDebug, false)
• 🔧 Failure in Workflow: Process new code merged to main
• 🔗 Triggered by PR: PR Link
• 👤 PR Author: @Krishna2323
• 🤝 Merged by: @tgolen
• 🐛 Error Message:
  warning: Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135, actions/setup-java@c5195ef, aws-actions/configure-aws-credentials@ececac1, gradle/actions@ac638b0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
  failure: Process completed with exit code 1.
  warning: Back off 23.463 seconds before retry.
  warning: Failed to download action 'https://api.github.com/repos/actions/setup-java/tarball/c5195efecf7bdfc987ee8bae7a71cb8b11521c00'. Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
  warning: Back off 16.222 seconds before retry.
  warning: Failed to download action 'https://api.github.com/repos/actions/setup-java/tarball/c5195efecf7bdfc987ee8bae7a71cb8b11521c00'. Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.

⚠️ Action Required ⚠️:

🛠️ A recent merge appears to have caused a failure in the job named build (developmentDebug, false).
🔍 This issue has been automatically created and labeled with Workflow Failure for investigation.

👀 Please look into the following:

1. Why the PR caused the job to fail?
2. Address any underlying issues.

🐛 We appreciate your help in squashing this bug!