new workload router-perf-v3

We run `router-perf-v2` workload for data plane performance test and we need some enhancement to address a different behavior on managed-service OCP.
This workload creates pods and generates traffic within cluster (from `hostnet` pod) and on AWS Openshift http traffics from client get routed to an external `Loadbalancer` VIP and route back to the cluster.
But other platforms follow completely different approach, GCP/Azure route client traffics to their corresponding service `clusterIP` using IPtables DNAT policy, so the client traffic will not exit out of a cluster and reach server.

Probably its worth spending some effort on a new workload `router-perf-v3`(or add-on to v2) to run the client from an external source to replicate real-world scenario, however the consistency of results are affected due to known external variable(LB, client resources, client location, cloud variability), this way it follows same behavior on all platform and easier to compare results between them.