Description of problem:
When DPDK checkup setup fails (e.g. due to an invalid parameter in the ConfigMap, like in https://bugzilla.redhat.com/show_bug.cgi?id=2188244), the setup should occur immediately, and not wait for the configured timeout (which is set in the job's ConfigMap).

Version-Release number of selected component (if applicable):
CNV 4.14.0
container-native-virtualization/kubevirt-dpdk-checkup-rhel9:v4.14.0-116

How reproducible:
Always

Steps to Reproduce:
1.
Apply the attached resources in their numeric order.
$ oc apply -f 1-dpdk-checkup-mcp.yaml
$ oc apply -f 2-dpdk-checkup-performance-profile.yaml
...
Change the parameters according to your environment.
Note that the ConfigMap (6-dpdk-checkup-configmap.yaml) has this invalid parameter on purpose:
spec.param.trafficGenTargetNodeName: "invalid-node-name"

Actual results:
The job fails and teardown removes all created resources (pods and VMIs), but it only happens after the timeout that is configured in the ConfigMap (10 minutes in this example).

Expected results:
If an invalid parameter was entered and the checkup fails - it should fail immediately, including tearing down all the created resources.