chore(deps): update rpmlock (foreman-3.16)

[vkrizan]

Summary by Sourcery

Chores:

• Refresh rpms.lock.yaml to track the latest UBI9 Node.js stack, libbrotli, OpenSSL, and related module metadata for x86_64 images.

[sourcery-ai]

Reviewer's Guide

Updates the rpm lockfile for the foreman-3.16 build to newer UBI9 appstream/baseos artifacts, primarily bumping Node.js (and npm) plus a couple of base libraries, with corresponding metadata (sizes, checksums, EVR, source RPM, module metadata) refreshed to match the new UBI 9.7 repositories.

File-Level Changes

Change	Details	Files
Bump Node.js and npm RPMs to newer UBI 9.7 module versions and refresh their metadata.	Update nodejs, nodejs-docs, nodejs-full-i18n, nodejs-libs, and npm URLs to point to newer 22.22.0 / 10.9.4 module builds from el9.7 Adjust size and sha256 checksum fields to match the new RPM artifacts Update EVR strings and sourcerpm fields for all Node.js-related packages to align with the new module build	rpms.lock.yaml
Update base library RPM pins (libbrotli and openssl) to newer builds and refresh their metadata.	Change libbrotli URL to the 1.0.9-9.el9_7 build with updated size, checksum, EVR, and sourcerpm Change openssl URL to the 3.5.1-7.el9_7 build with updated size, checksum, EVR, and sourcerpm Remove explicit openssl-libs entry, relying on the dependency provided by the updated openssl package	rpms.lock.yaml
Refresh UBI appstream module metadata reference for the locked repository state.	Update module_metadata URL to point to the latest modules.yaml.gz from the UBI 9 appstream repo Adjust size and checksum of the module_metadata entry to match the new metadata file	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.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

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