Add support for NetworkPolicy to the v2 chart

[tongpu]

Describe the current behavior
When deploying the Azure Service Operator on a cluster with default deny NetworkPolicies for every namespace then the Kubernetes API service is unable to communicate with the operator pod.

Describe the improvement
Add support for deploying NetworkPolicies, which allow Ingress traffic to the pod and Egress from the pod.

Additional context
I have the required NetworkPolicies ready, but I'm unsure how the release process of the Helm chart works right now and would need some guidance on how to contribute this change.

[matthchr]

I looked and see that a number of other charts do have NetworkPolicies included (w/ a value to turn them off if desired), so it makes sense we should probably do that too.

If you're willing, you can send a PR to add the policies here.

They should have a guard like {{- if .Values.policies.create}}, which I believe it's safe to default to true in the values.yaml.

Much of the chart is generated based on our code-generator (including the CRDs themselves), but since these are static you shouldn't have to worry about that part at all.

The actual release process won't include them until the next generated chart (likely 2.3.0).