[8.10](backport #3691) ironbank: move to ubi9

[mergify]

This is an automatic backport of pull request #3691 done by Mergify.
Cherry-pick of a956f64 has failed:

On branch mergify/bp/8.10/pr-3691
Your branch is up to date with 'origin/8.10'.

You are currently cherry-picking commit a956f6436a.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .ci/Jenkinsfile
	modified:   dev-tools/dependencies-report
	modified:   dev-tools/packaging/packages.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   dev-tools/packaging/templates/ironbank/Dockerfile.tmpl
	both modified:   dev-tools/packaging/templates/ironbank/hardening_manifest.yaml.tmpl

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[mergify]

This pull request has not been merged yet. Could you please review and merge it @v1v? 🙏

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[elasticmachine]

❕ Build Aborted

Either there was a build timeout or someone aborted the build.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-11-06T20:23:56.221+0000

• Duration: 182 min 56 sec

Test stats 🧪

Test	Results
Failed	0
Passed	11050
Skipped	109
Total	11159

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	98.795% (82/83)	👍
Files	67.466% (197/292)	👍
Classes	65.751% (359/546)	👍
Methods	52.499% (1124/2141)	👍
Lines	38.163% (12819/33590)	👍 0.012
Conditionals	100.0% (0/0)	💚

[pierrehilbert]

/test

[v1v]

/test

[v1v]

build 2 failed since the m1 stage didn't provision any worker... maybe something related to Orka.

As far as I see m1 was disabled in Jenkins with #3573 but it has not been backported to 8.10, no clue whether it's needed but M1 workers cannot be provisioned in Jenkins.

[v1v]

Requires #3719

[v1v]

Likely this PR won't be needed if 8.11.0 is out

[pierrehilbert]

Let's close this then.