chore(ci): dynamically determine Chart version

[zdrapela]

Description

Please explain the changes you made here.

Which issue(s) does this PR fix

• Fixes #?

PR acceptance criteria

Please make sure that the following steps are complete:

• GitHub Actions are completed and successful
• Unit Tests are updated and passing
• E2E Tests are updated and passing
• Documentation is updated if necessary (requirement for new features)
• Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[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 gustavolira 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:

• .ibm/OWNERS

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

[zdrapela]

/test e2e-ocp-helm-upgrade-nightly

[zdrapela]

/test e2e-ocp-helm

[zdrapela]

/test e2e-ocp-helm-upgrade-nightly
/test e2e-ocp-helm

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-4209
• quay.io/rhdh-community/rhdh:pr-4209-24975d01

[subhashkhileri]

I think this might fail the job on the release branch if we plan to backport it. There’s a chance that the next release CV won’t appear in the first 100 batches of the API request. For the next tag, it should work fine since it gets built frequently.

[zdrapela]

This curl will be exercised only on the main branch, and I think that it's very unlikely, that the next (right now 1.10.) wouldn't show up in the first 100.
If we're on the release-x.y branch, it will just cut the x.y from the branch name and search for the tag using a filter the tags that contains x.y.

[github-actions]

🚫 Image Push Skipped.

The container image push was skipped because the build was skipped (either due to [skip-build] tag or no relevant changes with existing image)

[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

[openshift-ci]

@zdrapela: The following test 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-ocp-helm	7fba4a8	link	true	/test e2e-ocp-helm

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.