Prune certain services from three KUTTL tests

[abays]

First pass at trying to prune some potentially unneeded services from the OpenStackControlPlane during KUTTL tests. The approach taken here showed a 10-15% performance boost.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abays

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [abays]

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

[stuggi]

the faster time of 10-15%, have we seen it when running on a local server or in ci? From this jobs logs, the overall time of the kuttl test seems to be not less than what we e.g. see in the current bump PR #1740.

• ci/prow/openstack-operator-build-deploy-kuttl

INFO[2025-12-16T20:16:48Z] Step openstack-operator-build-deploy-kuttl-openstack-k8s-operators-kuttl succeeded after 1h57m56s. 

vs.

INFO[2025-12-13T12:36:18Z] Step openstack-operator-build-deploy-kuttl-openstack-k8s-operators-kuttl succeeded after 1h56m59s. 

• ci/prow/openstack-operator-build-deploy-kuttl-4-18

INFO[2025-12-16T20:21:55Z] Step openstack-operator-build-deploy-kuttl-4-18-openstack-k8s-operators-kuttl succeeded after 2h2m19s. 

vs.

INFO[2025-12-13T12:33:07Z] Step openstack-operator-build-deploy-kuttl-4-18-openstack-k8s-operators-kuttl succeeded after 1h50m16s. 

[abays]

the faster time of 10-15%, have we seen it when running on a local server or in ci? From this jobs logs, the overall time of the kuttl test seems to be not less than what we e.g. see in the current bump PR #1740.

* ci/prow/openstack-operator-build-deploy-kuttl

INFO[2025-12-16T20:16:48Z] Step openstack-operator-build-deploy-kuttl-openstack-k8s-operators-kuttl succeeded after 1h57m56s. 

vs.

INFO[2025-12-13T12:36:18Z] Step openstack-operator-build-deploy-kuttl-openstack-k8s-operators-kuttl succeeded after 1h56m59s. 

* ci/prow/openstack-operator-build-deploy-kuttl-4-18

INFO[2025-12-16T20:21:55Z] Step openstack-operator-build-deploy-kuttl-4-18-openstack-k8s-operators-kuttl succeeded after 2h2m19s. 

vs.

INFO[2025-12-13T12:33:07Z] Step openstack-operator-build-deploy-kuttl-4-18-openstack-k8s-operators-kuttl succeeded after 1h50m16s. 

Local server. And in that case, I am testing using make openstack_kuttl_run, so I am atomically targeting just the KUTTL tests without considering the infrastructure spin-up. In a CI environment, there's far more variability because those times you cited encompassing the entire process (and not just the KUTTL tests themselves). Also, I imagine that cloning repos and pulling contain images in CI can vary based on incidental network speed, which is another variable I eliminated in my local testing by using the specific make openstack_kuttl_run.