chore(deployment): pin ubuntu version used by github (#30871)

[dcolina]

Proposed Changes

• This pull request proposes updating all Ubuntu runners in our CICD pipelines to version 24.04.
• A new GitHub repository variable is needed. UBUNTU_RUNNER_VERSION must be set to 24.04; otherwise, workflows will default to using 22.04.

Details

We conducted thorough testing with the following setups:

Ubuntu 22.04:

• Executed main CICD workflows (PR, Merge Queue, Trunk, and Nightly) on fork.
  All runs completed successfully without any unusual behavior.

Ubuntu 24.04:

• Repeated the same tests with runners updated to 24.04.
  Similarly, all workflows ran correctly, with no anomalies observed.

Proposal

• Given the successful results in both cases, we propose setting the runners directly to version 24.04 to streamline the update process.

Next Steps

• Merge this PR to update the Ubuntu runners.
• Monitor post-deployment to ensure stability across all workflows.

Fixes

#30871

This PR fixes: #30871

[victoralfaro-dotcms]

@dcolina thank you for all these changes.
This has grown enough to make me wonder if we could take this opportunity to actually store this ubuntu version as a repo ENVIRONMENT VARIABLE.
At the workflows we could reference it like this:

  runs-on: ubuntu-{{ vars.UBUNTU_MAIN_VERSION }} # or any other name since I'm terrible at naming

This way we could make the change in one single place without introducing any code changes in the future. We can also manage several versions since some workflows (can't recall which ones) work better with specific ubuntu versions.

[sfreudenthaler]

Requests

• Requested some changes with the readme's
• Did you manually test the fallback in the forked repo to make sure it works?

Questions that are not blockers

• When will we remove the fallback, or at least update it to fallback to 24.04 if no var provided?
• is there some way to define the full runs on value ubuntu-${{ vars.UBUNTU_RUNNER_VERSION || '22.04' }} once and have it inherited downstream? Just trying to keep pushing to fewer places we have to repeat ourselves :)

[dcolina]

• All the readme file (examples) have been updated.
• Fallback was manually tested in the forked repo.
• Fallback has been set to 24.04
• There is no straightforward or simple way to define the runs-on configuration in a single location and reference it across all workflows in the project. The available alternatives would require significantly more changes than we’d prefer, and they do not fully provide the desired solution—at least from a development perspective.

[sfreudenthaler]

Looks great. Thanks for the changes and thoughts