Add azure cni specific network policies to azure cni e2e tests

[nawazkh]

/kind feature

Describe the solution you'd like [A clear and concise description of what you want to happen.]

• Add azure cni specific network policies to azure cni e2e tests.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

• PR https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/3508 adds azure cni v1 e2e tests using one NIC per linux nodes. We should be extending this test to add network policies specific to Azure CNI v1 tests.
• Also note, since the CIDR of the IPs assigned to the pods changes depends on the user (if specified), default network policies as defined in the e2e tests may not work by merely extending the framework.

Environment:

• cluster-api-provider-azure version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten