feat: Added support for openshift-ai-addon version 417 and 418

[zikra-iqbal]

Description

Added support for openshift-ai-addon versions:

openshift-ai 416
Supported OpenShift cluster versions: >=4.16.0 <4.18.0

openshift-ai 417
Supported OpenShift cluster versions: >=4.17.0 <4.19.0

openshift-ai 418
Supported OpenShift cluster versions: >=4.18.0 <4.20.0

Documentation link

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Added support for openshift-ai-addon versions 416 and 417.

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[zikra-iqbal]

Scenario-1:

ocp_version = "4.18"
"openshift-ai" = {
      version = "416"
    } 

Scenario-2:

ocp_version = "4.15"
"openshift-ai" = {
      version = "416"
    } 

Scenario-3:

ocp_version = "4.19"
"openshift-ai" = {
      version = "417"
    } 

Scenario-4:

ocp_version = "4.16"
"openshift-ai" = {
      version = "417"
    } 

[zikra-iqbal]

Scenario-5:

ocp_version = "4.18"
"openshift-ai" = {
      version = "417"
    } 

[zikra-iqbal]

Scenario-6:

ocp_version = "4.16"
"openshift-ai" = {
      version = "416"
    } 

[zikra-iqbal]

/run pipeline

[Aashiq-J]

/run pipeline

[Khuzaima05]

/run pipeline

[vkuma17]

1 minor comment

[Khuzaima05]

/run pipeline

[Khuzaima05]

Add on test is failing :

re-running

[Khuzaima05]

Again Failing with same add-on test failure un-related to this PR:

[Khuzaima05]

/run pipeline

[Khuzaima05]

/run pipeline

[Khuzaima05]

/run pipeline

[Khuzaima05]

/run pipeline

[Khuzaima05]

/run pipeline

[Khuzaima05]

/run pipeline

[Khuzaima05]

/run pipeline

[ocofaigh]

I don't think we should go with this approach. Too much overhead on us. Instead there is an api we can use. Whatever api the CLI command ibmcloud oc cluster addon versions --output json is using, we should use an external data block (so its run at plan time) and create a script to validate.
It might be easier to implement in python too.

[Khuzaima05]

Closing this PR, as we’ve decided not to proceed with the manual validation approach. Instead, we’ll implement an API-based solution as discussed here #866 (review) . That work will be handled under this issue: https://github.ibm.com/GoldenEye/issues/issues/16974