Use Dedicated Namespace for Resources

[danehans]

The POC readme and e2e tests use the "default" namespace. To follow Kubernetes' best practices and preserve the "default" namespace, a dedicated namespace, i.e. inf-ext-e2e, should be used throughout.

[kfswain]

I think it's reasonable for a getting started guide to utilize the default namespace, I think its acceptable to expect the user to know how to deploy in a specific namespace should they desire, and it lets the getting started manifests be that much cleaner. Open to alt opinions however, LMKWYT!

[nirrozenbaum]

I tend to agree with @danehans.
almost every CNCF project I worked with has a dedicated ns for it’s resources.

[kfswain]

Which resources would we tuck into a specific namespace? The current expectation is that the user deploys the EPP themselves. We don't really have other deployables atm

For the Getting Started i think its fine to leave default and not make opinionated decisions for a guide of that format.

[danehans]

This issue was partially resolved when the EPP Helm chart was introduced. However, e2e is still bound to namespace default due to the Envoy ConfigMap containing namespace-specific values, e.g. authority: vllm-llama3-8b-instruct-epp.default:9002. As an initial solution, we should change the e2e namespace (default) to something specific for e2e testing, update the Envoy ConfigMap accordingly, and have the e2e suite create the e2e namespace.