Discuss with stakeholders to verify these user stories:

• As an app developer, I want Istio to not inject sidecars into my application pods

• As an project admin, I want to create a gateway, attach routes to it, have Istio/envoy route ingress traffic according to the Gateway/HTTPRoute specifications

In other words, and in combination, I want Istio to inject envoy exactly when needed (only for Gateways).

For the cases where we need to install within OSSM, we need to install without sidecars enabled.  In other words, we need to install north-south gateway function only, NOT east-west. 

Check with Rob on "As a point of clarification, mesh related features, namely sidecar injection for specific namespaces, would only be provided on an opt-in basis, meaning that the above install procedure would only allow the control plane to manage pods created through the Gateway api (i.e. no other injection would occur)." and show this is still works in selected image for tech preview.

Deliverable includes any necessary yaml to configure the desired behavior

[stretch goal] should inform an e2e test that verifies this behavior
Edit: Added https://issues.redhat.com/browse/NE-1125 to accomplish this stretch goal.