Currently some router tests in openshift/origin are skipped in the e2e-aws-proxy job.

These tests are skipped by the CI job itself, and not by any logic in the origin tests to detect if a cluster-wide egress proxy is in use.

These tests cannot be re-enabled given that the current e2e-aws-proxy workflow sets up a squid egress proxy, and squid does not allow setting custom client-side host headers (which the tests rely on).

Ideally we would add logic to openshift/origin to detect if the cluster-wide egress proxy is in use and skip the tests when appropriate (rather than force-skip them in the CI job definition).

See https://bugzilla.redhat.com/show_bug.cgi?id=1882486 for more context.