feat: Replace ubi9 with ubi10

[NickLarsenNZ]

Resolves #1349.

Description

Caution

This is WIP. Still fixing things locally

todo: add bit about daemontools

Definition of Done Checklist

Note

Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant.

Please make sure all these things are done and tick the boxes

• Changes are OpenShift compatible
• All added packages (via microdnf or otherwise) have a comment on why they are added
• Things not downloaded from Red Hat repositories should be mirrored in the Stackable repository and downloaded from there
• All packages should have (if available) signatures/hashes verified
• Add an entry to the CHANGELOG.md file
• Integration tests ran successfully

TIP: Running integration tests with a new product image

The image can be built and uploaded to the kind cluster with the following commands:

boil build <IMAGE> --image-version <RELEASE_VERSION> --strip-architecture --load
kind load docker-image <MANIFEST_URI> --name=<name-of-your-test-cluster>

See the output of boil to retrieve the image manifest URI for <MANIFEST_URI>.

[NickLarsenNZ]

Previously we installed nodejs:${VERSION} via DNF modules. DNF modules are obsolete.
Now we have these options:

• Install the latest available node package
• Install a specific node package via the full name
• Install a version manager (eg: nvm) to set the version that the version of the product requires.

In a similar vein, python3.11 is no available, but I see python3-3.12.11. So we have these options:

• Install the latest available python package
• Install a specific python package via the full name
• Install a version manager (eg: uv venv --python 3.11) to set the version that the version of the product requires.

[NickLarsenNZ]

Well

[root@c9e4e15b7e89 /]# npm install -g nvm
npm warn deprecated nvm@0.0.4: This is NOT the correct nvm. Visit https://nvm.sh and use the curl command to install it.

[NickLarsenNZ]

nvm appears to be a script or set of scripts), so I think we either need to:

• Upload (via script) the latest archive to Nexus, or
• Leverage patchable (and create a fork) to do all of this withing the repo without having to interact with Nexus.

[NickLarsenNZ]

I pushed my WIP commits since we have the on-site and I might lose track of where I was at.

I think we should use uv to completely manage the python version being used during the build and in the resulting image.

Per 538b3ba, I have tested oldest and newest airflow (via getting_started) and it ran fine. The build stage needs similar treatment as the final stage.