fix(nvca-operator): use NGC core BYOO image

[kristinapathak]

TL;DR

Route the staging BYOO OpenTelemetry Collector default to the NGC core repository so NCP function and task sidecars use the repository granted to their deployment credential.

Additional Details

The chart derived the staging collector location from the operator repository. This selected a different repository from the one configured for the collector artifact.

The source chart and generated release chart now use stg.nvcr.io/nv-cf/nvcf-core/byoo-otel-collector for staging defaults. Explicit BYOO collector image overrides still take precedence.

For the Reviewer

Please review the staging fallback and its rendered-image regression assertion.

For QA

• make test-self-managed-nvca-image-reference
• make lint
• make test-release-image-manifest

QA needed: No. The chart rendering test covers both function and task overrides.

Issues

Relates to #1039

Checklist

• I am familiar with the Contributing Guidelines.
• I have signed off my commits for Developer Certificate of Origin (DCO) compliance.
• New or existing tests cover the update.
• The documentation is up to date with the update.

Github commit:

5117640

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 6153326e-1643-423d-b11d-950623ed9498

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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