Do not run functional test during docker build

[gibizer]

The functional test can be unstable causing the docker build to fail and that makes the content provider job failing and blocking CI.

We have a separate functional job to run these tests that should be enough.

The unstable functional test needs to be fixed separately

[lewisdenny]

/approve

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abays, gibizer, lewisdenny

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](https://github.com/openstack-k8s-operators/openstack-operator/blob/main/OWNERS)~~ [abays,lewisdenny] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[gibizer]

/test openstack-operator-build-deploy-kuttl

Removing debug pod ...
error: unable to upgrade connection: container container-00 not found in pod oko-12-xzvvk-master-1-debug-sk52g_openstack-kuttl-tests
make[3]: *** [Makefile:558: crc_storage] Error 1
make[3]: Leaving directory '/alabama/install_yamls'
Failed to run 'make crc_storage' target. Aborting

[softwarefactory-project-zuul[bot]]

Build failed (check pipeline). Post recheck (without leading slash) to rerun all jobs. Make sure the failure cause has been resolved before you rerun jobs.

https://review.rdoproject.org/zuul/buildset/6a66608313074b198f94a78d9f615a77

:heavy_check_mark: openstack-k8s-operators-content-provider SUCCESS in 1h 42m 47s :heavy_check_mark: podified-multinode-edpm-deployment-crc SUCCESS in 1h 25m 31s :heavy_check_mark: cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 18m 52s :x: openstack-operator-tempest-multinode RETRY_LIMIT in 6s

[gibizer]

recheck retry limit