Disable periodic Prow jobs that make use of the `aws` cluster profile

[rm3l]

/area testing /kind task /priority High

We are asked to move away from using the aws cluster profile and find/create a new one from our organization, for infra cost reasons.

As discussed in our community call (Oct 09, 2023), it makes sense for odo to remove our periodic Prow runs (the ones that were using the aws cluster profile) as they don't seem to be that useful anyway. We already have good coverage with the checks that we run on IBM Cloud.

NOTES:

• As discussed in the community call, we need to check the profile used for running interop tests, and how they might be affected by this. Update: remove only the periodic runs using the aws cluster profile, not the ones using the aws-cspi-qe cluster profile (which are used for interop tests and managed by a different team).

Related to https://github.com/redhat-developer/odo/issues/7110

[rm3l]

PR created: https://github.com/openshift/release/pull/44645

[rm3l]

PR merged in the openshift/release repo. Leaving this issue open for now, to make sure that no periodic job runs tomorrow.

[rm3l]

/close All periodic jobs on Prow using the aws cluster profile are now disabled.