Update registry.access.redhat.com/ubi9/nodejs-22 Docker tag to v9

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
registry.access.redhat.com/ubi9/nodejs-22	stage	major	1-1783573424 → 9.8-1783903054

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the frontend Docker image base for the Node.js 22 UBI9 stage from tag 1-1783573424 to 9.8-1783573424, aligning with a newer major image version.

File-Level Changes

Change	Details	Files
Update Node.js 22 UBI9 base image tag used in the frontend Docker build stage to a newer major version.	Change the Docker image tag for the Node.js 22 UBI9 stage from 1-1783573424 to 9.8-1783573424. Ensure the updated image reference remains under the same registry and repository path. No other Dockerfile stages or build arguments are modified.	frontend/docker/Dockerfile.frontend

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since this is a major base image bump, verify that any Node/npm/yarn tooling or build scripts in the frontend Dockerfile are still compatible with the new UBI9 nodejs-22 image (e.g., default working directory, user, and installed tools).
• If other Dockerfiles or CI pipelines rely on the previous 1-1783573424 tag, consider updating them in the same change to keep the environment consistent and avoid subtle differences between builds.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since this is a major base image bump, verify that any Node/npm/yarn tooling or build scripts in the frontend Dockerfile are still compatible with the new UBI9 nodejs-22 image (e.g., default working directory, user, and installed tools).
- If other Dockerfiles or CI pipelines rely on the previous `1-1783573424` tag, consider updating them in the same change to keep the environment consistent and avoid subtle differences between builds.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.06%. Comparing base (139b50e) to head (dc6df60).

❌ Your project check has failed because the head coverage (62.06%) is below the target coverage (85.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #937   +/-   ##
=======================================
  Coverage   62.06%   62.06%           
=======================================
  Files          91       91           
  Lines        3978     3978           
=======================================
  Hits         2469     2469           
  Misses       1509     1509           

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 139b50e...dc6df60. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.