Refactor and rename test case networking-dpdk-cpu-pinning-exec-probe

[greyerof]

This task has two goals:

1. Renaming the tc networking-dpdk-cpu-pinning-exec-probe to avoid any reference to "dpdk" and move it to a different tc since it won't suite well in the networking one.

Proposed new identifier: cpu-pinning-no-exec-probes
Proposed test suite: performance
Full test case name: performance-cpu-pinning-no-exec-probes

2. Refactor the tc to avoid searching for "dpdk" drivers installed in the node where workload pods under test are running as a precondition to filter the pods under test.

Currently, exec probes are only checked on pods with CPU pinning (Guaranteed QoS with exclusive CPUs) that also have the vfio-pci module installed on the node.The proposed refactoring aims to remove the filterDPDKRunningPods function. This change would allow exec probes check to be performed on any Guaranteed QoS pod utilizing exclusive CPUs. The rationale behind this is that any workload requiring exclusive CPUs inherently indicates a need for non-interruptible task execution. DPDK-based workloads, which are a subset of such tasks, will always operate on exclusive CPUs.

The test case description and remediation must also be updated to reflect this change.
QE test cases might also need to be updated.

[acornett21]

Renaming could possibly cause in CI failures and the QE project might need updates as well.

• https://github.com/redhat-best-practices-for-k8s/certsuite-qe

[rocrisp]

The QE project has a new PR for this refactor change.