fix(orchestrator-infra): Rename the chart in the README [RHDHBUGS-2021]

[rm3l]

Description of the change

The chart was renamed in [1][2], but the README was still pointing to the
previous chart, which caused users to install an outdated version of the
chart when following this doc.

[1] https://issues.redhat.com/browse/RHIDP-6169
[2] #131

Which issue(s) does this PR fix or relate to

• Fixes https://issues.redhat.com/browse/RHDHBUGS-2021

How to test changes / Special notes to the reviewer

—

Checklist

• For each Chart updated, version bumped in the corresponding Chart.yaml according to Semantic Versioning.
• For each Chart updated, variables are documented in the values.yaml and added to the corresponding README.md. The pre-commit utility can be used to generate the necessary content. Use pre-commit run -a to apply changes. The pre-commit Workflow will do this automatically for you if needed.
• JSON Schema template updated and re-generated the raw schema via the pre-commit hook.
• Tests pass using the Chart Testing tool and the ct lint command.
• If you updated the orchestrator-infra chart, make sure the versions of the Knative CRDs are aligned with the versions of the CRDs installed by the OpenShift Serverless operators declared in the values.yaml file. See Installing Knative Eventing and Knative Serving CRDs for more details.

Summary by Sourcery

Update orchestrator-infra chart references in documentation and bump chart version to align with recent renaming

Bug Fixes:

• Fix outdated helm chart reference in the orchestrator-infra README

Build:

• Bump orchestrator-infra chart version to 0.2.2

Documentation:

• Update README badge and helm install command to use the renamed chart

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rm3l]

/cherry-pick release-1.7

[sourcery-ai]

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

[openshift-cherrypick-robot]

@rm3l: once the present PR merges, I will cherry-pick it on top of release-1.7 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-1.7

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.

[rm3l]

This is just a simple fix in the README - so merging to close the issue.

[openshift-cherrypick-robot]

@rm3l: #236 failed to apply on top of branch "release-1.7":

Applying: fix(orchestrator-infra): Rename the chart in the README template
Applying: Apply pre-commit hooks
Using index info to reconstruct a base tree...
M	charts/orchestrator-infra/Chart.yaml
M	charts/orchestrator-infra/README.md
Falling back to patching base and 3-way merge...
Auto-merging charts/orchestrator-infra/README.md
CONFLICT (content): Merge conflict in charts/orchestrator-infra/README.md
Auto-merging charts/orchestrator-infra/Chart.yaml
CONFLICT (content): Merge conflict in charts/orchestrator-infra/Chart.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 Apply pre-commit hooks

Details

In response to this:

/cherry-pick release-1.7

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.