Running cnf-tests image after the split is not aligning with the old options described in the official docs:

Junit file doesn’t actually work, no test report is collected:
[root@cnfdr23 ~]# podman run -v ~/.kube/:/kubeconfig:Z -v $(pwd)/junit:/junit -e KUBECONFIG=/kubeconfig/config -e IMAGE_REGISTRY=registry-proxy.engineering.redhat.com/rh-osbs/ -e CNF_TESTS_IMAGE=openshift4-cnf-tests:v4.15.0-17 -e LATENCY_TEST_CPUS=4 -e LATENCY_TEST_RUNTIME=1 -e MAXIMUM_LATENCY=2000000 registry-proxy.engineering.redhat.com/rh-osbs/openshift4-cnf-tests:v4.15.0-17 /usr/bin/test-run.sh --ginkgo.vv --junit /junit

Tests skipped by default if we don’t pass env vars:
[root@cnfdr23 ~]# podman run -v ~/.kube/:/kubeconfig:Z -v $(pwd)/junit:/junit -e KUBECONFIG=/kubeconfig/config -e IMAGE_REGISTRY=registry-proxy.engineering.redhat.com/rh-osbs/ -e CNF_TESTS_IMAGE=openshift4-cnf-tests:v4.15.0-17 registry-proxy.engineering.redhat.com/rh-osbs/openshift4-cnf-tests:v4.15.0-17 /usr/bin/test-run.sh --ginkgo.vv --junit /junitrunning /usr/bin/latency-e2e.testRunning Suite: Performance Addon Operator latency e2e tests - /===============================================================Random Seed: 1705057165
Will run 3 of 3 specsSSS
Ran 0 of 3 Specs in 6.065 secondsSUCCESS! -- 0 Passed | 0 Failed | 0 Pending | 3 Skipped
 But no info is provided. The user should be able to understand why the tests were skipped. 

    4.15

    always

    1.run podman command with the new cnf-tests image, execlude 4.15.0-18 as it is very old. use 4.15.0-17.
    2.
    3.
    

    ginkgo missing attributes using podman: focus on specific test, ginkgo verbosity. also missing to gather the tests reports to junit file. 

    running the new image should still provide the option to focus, and test verbosity and allow to store test report in junit file.