chore: Make sure ct lint runs against all charts

[rm3l]

Description of the change

Otherwise, we might miss some required version bumps on the previously-excluded charts, like in https://github.com/redhat-developer/rhdh-chart/actions/runs/17655946490/job/50178635934?pr=239#step:8:26 where it skipped a chart that actually requires a version bump.

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

https://github.com/redhat-developer/rhdh-chart/actions/runs/17655946490/job/50178635934?pr=239#step:8:26

How to test changes / Special notes to the reviewer

We can see in https://github.com/redhat-developer/rhdh-chart/actions/runs/17656363770/job/50179970842?pr=243 that all modified charts are being linted.
And in https://github.com/redhat-developer/rhdh-chart/actions/runs/17656363790/job/50179971216?pr=243#step:14:28, we can see that only the non-excluded charts modified are being tested.

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 chart-testing configuration and workflow to lint all charts with a dedicated config file and apply minor README adjustments across multiple chart directories

Enhancements:

• Introduce ct-lint.yaml to define chart directories, disable maintainer validation, set remote origin, and extend Helm timeout

CI:

• Switch GitHub Actions lint job to use ct-lint.yaml instead of ct.yaml

Documentation:

• Normalize casing in the Backstage chart README
• Add placeholder comments in orchestrator and software templates chart READMEs

Summary by Sourcery

Ensure chart linting runs against all charts by creating a dedicated configuration file and updating the CI workflow.

Enhancements:

• Introduce ct-lint.yaml to specify all chart directories, disable maintainer validation, set the remote origin, and increase Helm timeout

CI:

• Switch the GitHub Actions lint job to use ct-lint.yaml instead of ct.yaml

[github-actions]

⚠️ Files changed after running the pre-commit hooks

Those changes should have been pushed automatically to your PR branch.

NOTE: If the PR checks are stuck after this additional commit, manually close the PR and immediately reopen it to trigger the checks again.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• Remove or deprecate the original ct.yaml and update any references so there's no confusion now that ct-lint.yaml is your primary config.
• Add a brief inline note in ct-lint.yaml explaining why 'validate-maintainers' is disabled to give future contributors context.
• Consider exposing the Helm timeout value as a CI variable instead of hardcoding 500s, which makes it easier to adjust per chart or per environment.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- Remove or deprecate the original ct.yaml and update any references so there's no confusion now that ct-lint.yaml is your primary config.
- Add a brief inline note in ct-lint.yaml explaining why 'validate-maintainers' is disabled to give future contributors context.
- Consider exposing the Helm timeout value as a CI variable instead of hardcoding 500s, which makes it easier to adjust per chart or per environment.

---

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

[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