chore(deps): update registry.access.redhat.com/ubi9/ubi-minimal docker digest to 186a94b (foreman-3.18)

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
registry.access.redhat.com/ubi9/ubi-minimal	final	digest	d235f60 → 186a94b
registry.access.redhat.com/ubi9/ubi-minimal	stage	digest	d235f60 → 186a94b

---

Configuration

📅 Schedule: (in timezone Europe/Prague)

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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.

Summary by Sourcery

Update the UBI 9 minimal container base image and its associated package metadata lock.

Build:

• Update the UBI 9 minimal base image digest used for both build and runtime container stages.

Chores:

• Refresh the locked RHEL module metadata checksum to match the updated base image.

[sourcery-ai]

Sorry @red-hat-konflux[bot], you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 2 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the foreman-3.18 container to UBI 9 minimal digest 186a94b for both build and runtime stages, and refreshes the corresponding locked RHEL AppStream module metadata.

File-Level Changes

Change	Details	Files
Pin both build and runtime stages to the updated UBI 9 minimal image digest.	Replace the previous UBI image digest in both multi-stage FROM instructions. Retain identical build and runtime image structure while consuming the refreshed base image.	Dockerfile
Refresh RPM module metadata associated with the updated base-image dependency set.	Update the RHEL 9 AppStream module metadata URL and matching SHA-256 checksum.	rpms.lock.yaml

---

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.