PODAUTO-228: Upstream rebase to 2.15.1

[jkyros]

1. Create a rebase tree using rebasebot:

rebasebot --source https://github.com/kedacore/keda:release/v2.15 --dest openshift/keda:main \
  --rebase jkyros/keda:rebase-2.15 --tag-policy=strict --update-go-modules --dry-run \
 --github-user-token ~/githubtoken

2. Check all "numbered carry PRs", rebasebot likes to drop them regardles (looked like they were all legit drops)
3. Update .ci-operator.yaml to reference rhel-9-release-golang-1.22-openshift-4.18 (vs 4.17, moving to go 1.22 finally)
4. Squash duplicate carry commits (OWNERS, .ci-operator.yaml, e2e hacks)
5. Add verify history drop commit to use upstream's release/v2.15 branch as the merge base
6. Push to own fork, open PR

[openshift-ci-robot]

@jkyros: This pull request references PODAUTO-228 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

1. Create a rebase tree using rebasebot:

rebasebot --source https://github.com/kedacore/keda:release/v2.15 --dest openshift/keda:main \
 --rebase jkyros/keda:rebase-2.15 --tag-policy=strict --update-go-modules --dry-run \
--github-user-token ~/githubtoken

2. Check all "numbered carry PRs", rebasebot likes to drop them regardles (looked like they were all legit drops)
3. Update .ci-operator.yaml to reference rhel-9-release-golang-1.22-openshift-4.18 (vs 4.17, moving to go 1.22 finally)
4. Squash duplicate carry commits (OWNERS, .ci-operator.yaml, e2e hacks)
5. Add verify history drop commit to use upstream's release/v2.15 branch as the merge base
6. Push to own fork, open PR

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkyros

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jkyros]

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

[jkyros]

Made it past the azure test, but it looks like we failed the persistentLag part of the kafka test (which didn't change, but some tests did get added before it, so maybe they aren't returning the environment to the proper state?)

    kafka_test.go:671: 
        	Error Trace:	/src/tests/scalers/kafka/kafka_test.go:671
        	            				/src/tests/scalers/kafka/kafka_test.go:459
        	Error:      	Should be true
        	Test:       	TestScaler
        	Messages:   	replica count should be 1 after 2 minute
    helper.go:845: No pods with label app=kafka-consumer
    helper.go:626: Applying template: singleDeploymentTemplate
    helper.go:502: Waiting for deployment replicas to hit target. Deployment - kafka-test-deployment, Current  - 1, Target - 1
    helper.go:560: Waiting for some time to ensure deployment replica count doesn't change from 1

Let's see if that's a flake...
/retest-required

[openshift-ci]

@jkyros: 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/keda-e2e-aws-ovn	ec83452	link	true	/test keda-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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.