chore(deps): update own-app-lightspeed-rag-content to 73fe32b

[red-hat-konflux]

Image created from 'https://github.com/openshift/lightspeed-rag-content?rev=9b82bc57f0ec5ef163c2cc7574587e5fc5037840'

This PR contains the following updates:

Package	Update	Change
quay.io/redhat-user-workloads/crt-nshift-lightspeed-tenant/own-app-lightspeed-rag-content	digest	d78b0dc -> 73fe32b

---

Configuration

📅 Schedule: 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 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

Summary by CodeRabbit

• Chores
  • Updated container image dependencies to the latest pinned versions.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tisnik for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 6a67b012-7161-4b94-9230-236c605de858

📥 Commits

Reviewing files that changed from the base of the PR and between c53631f and fc2cc8c.

📒 Files selected for processing (1)

• Containerfile

---

📝 Walkthrough

Walkthrough

This PR updates the pinned container image digest for the Lightspeed RAG content image in the Containerfile build configuration.

Changes

Lightspeed RAG Content Image Update

Layer / File(s)	Summary
Lightspeed RAG content image digest Containerfile	The LIGHTSPEED_RAG_CONTENT_IMAGE build argument is updated to a new pinned sha256 digest in the container build configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openshift/lightspeed-service#2942: Updates pinned image digests in .tekton/* PipelineRun task bundle references, following a similar pattern of updating build configuration image references.

Suggested labels

lgtm

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating a dependency pin in the Containerfile from one digest to another.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/component-updates/lightspeed-service-component-update-own-app-lightspeed-rag-content

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

@red-hat-konflux[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-ols-cluster	fc2cc8c	link	true	/test e2e-ols-cluster
ci/prow/integration	fc2cc8c	link	true	/test integration

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.