Unset resources section in workflows

[lpiwowar]

There is a bug in Tempest which prevents us to set a sane upper limit to the amount of memory Tempest can consume [1]. Until the fix reaches the upstream build of the openstack-tempest-all image we should not be setting any resource limits to the tempest pods.

This commit is ensuring that we are unsetting the default values set on the side of the test-operator in the workflow section of Tempest CR.

[1] https://bugs.launchpad.net/tempest/+bug/2088074
Related-Issue: https://issues.redhat.com/browse/OSPCIX-630

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[lpiwowar]

Testing here -> openstack-k8s-operators/test-operator#273

[karelyatin]

/lgtm

[lpiwowar]

Tested here -> openstack-k8s-operators/test-operator#273

We can see that the resources section got unset even in workflow section -> https://logserver.rdoproject.org/73/273/fb7ec89d375795c972ada38b456aa3317248a600/github-check/podified-multinode-edpm-deployment-crc-test-operator/9868c05/controller/ci-framework-data/logs/openstack-k8s-operators-openstack-must-gather/namespaces/openstack/crs/tempests.test.openstack.org/tempest-tests-tempest.yaml

[pablintino]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pablintino

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 [pablintino]

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