Use maxConnection=-1 in router-perf test to increase tps and reduce error connections

@rsevilla87 Hi Raul, in this bug comment https://bugzilla.redhat.com/show_bug.cgi?id=1983751#c7, I verified that with configuring maxConnection=-1, we can reduce lot's of '0' response number, increase '200' response number, as well as increasing TPS and reduce latency.
More test data and charts can be found here
https://docs.google.com/spreadsheets/d/1jNYCdTu2XvSs4xARk8PwQGoPZVgra0jOQORIlUKAdKg/edit#gid=1789221797

Please let me know what you think about adding this configuration to router-perf test as an ENV var and set it to default.

Please notice that maxConnection=-1 will cause the router pod to consume more cpu and memory.
In my test result above, I used
INFRA_NODE_INSTANCE_TYPE=m5.12xlarge (32x128)
WORKLOAD_NODE_INSTANCE_TYPE=m5.8xlarge (48x192)
I saw https://github.com/cloud-bulldozer/airflow-kubernetes/pull/190 tried to change Infrastructure nodes shifting from 48x192 to 16x64, that may need to be reevaluate if using this configuration.