Use stale container image with AlmaLinux 9.2 and working dependencies

[claraberendsen]

Description

With the new release of AlmaLinux 9.3 EPEL has made breaking changes to the upstream dependencies that due to

• 727

has rendered impossible to build on-demand new RHEL images.

To get ci back working this PR fetches prebuilt container images built before of the release that contain the correct dependencies. This is not a preferred state for running ci and these changes will affect us more deeply on build.ros2.org however until the drift of dependencies gets resolved upstream it's an acceptable compromise to keep running ci for RHEL.

Affected jobs on ci.ros2.org

• RHEL CI jobs
• RHEL nightlies
• RHEL packaging jobs

Testing

Strategy

• Deploy changes only to test jobs
• Build with RHEL 9.2-pinned build args

Test new default config return green ci

test_packaging_linux-rhel test_ci_linux-rhel

Test if statement shifts to other el releases when not in pinned version

[!NOTE]
The failure is expected here it shows that it's not using the default image

test_packaging_linux-rhel test_ci_linux-rhel

[claraberendsen]

What do you think?

I like the idea since it would give us more flexibility to test whenever the dependencies can be updated and gives developers the chance of changing according to need. It's definitely less breaking than the current implementation. The only thing that concerns me is that whenever things are fixed we should clean-up that option, but that is payload on our side to keep things in order.

[claraberendsen]

There's one outstanding comment which was already addressed on the ci_linux template but this is ready otherwise.

Addressed in https://github.com/ros2/ci/pull/728/commits/dfab04bf911fa9e74b2b8b82a57bd799cc18c6ab

[claraberendsen]

Now that CI has returned :green_circle: I will deploy on the RHEL jobs on ci.ros2.org and merge.

[claraberendsen]

Deployed with regexp '.*-rhel' to modify only rhel jobs. Final test on a ci_linux-rhel job