Is your feature request related to a problem? Please describe.

#66 introduced the new operator to UDS Core but does not include UDS Package CRs for istio or pepr components. While the ordering of deployment may make these more difficult it seems wise to include network policies (and other future benefits of the CR) for each of these.

Describe the solution you'd like

Ideally the istio charts and pepr itself deploy with their own UDS Package CRs. One thing we need to be careful to avoid is blocking/impacting the operator's ability to perform all necessary tasks.

Possibly we could deploy the CRD before all other components (similar to how prometheus CRDs are handled). Alternatively we could deploy Pepr before istio and most of the timing should work out.

Describe alternatives you've considered

1. Network policies and any other necessary objects could be created/deployed "manually" rather than via the operator. While this would work and sidestep the timing considerations it feels strange to not leverage the operator's benefits.
2. Leave these unprotected with no network policies. While this is the easiest answer I do think its at least worth exploring what network policies would work for istio/pepr and seeing if they have any tangible benefits before dismissing it entirely.