WIP:✨ Phase 1: Add Network Policy

[camilamacedo86]

This PR replaces the kube-rbac-proxy usage with NetworkPolicy
See that we are:

• Adding a protection using NetworkPolicies and update the docs
• Update the e2e tests to use Callico and we are able to ensure that the metrics endpoint is protected.

Motivations

**To understand why it is required see **: https://github.com/kubernetes-sigs/kubebuilder/blob/master/designs/discontinue_usage_of_kube_rbac_proxy.md

• Closes: use a NetworkPolicy instead of kube-rbac-proxy #1885
• Part of: [META - Phases]: Discontinue Kube RBAC Proxy in Default Kubebuilder Scaffolding #3871

What is missing to get done
If we have webhooks scaffold in the project after apply the policy in the namespace we will face issues within. So, we probably need to scaffold a policy for webhooks

kubectl -n e2e-jpwo-system apply -f config/samples/barjpwo_v1alpha1_foojpwo.yaml failed with error: (exit status 1) Error from server (InternalError): error when creating "config/samples/barjpwo_v1alpha1_foojpwo.yaml": Internal error occurred: failed calling webhook "mfoojpwo.kb.io": failed to call webhook: Post "[https://e2e-jpwo-webhook-service.e2e-jpwo-system.svc:443/mutate-barjpwo-example-comjpwo-v1alpha1-foojpwo?timeout=10s](https://e2e-jpwo-webhook-service.e2e-jpwo-system.svc/mutate-barjpwo-example-comjpwo-v1alpha1-foojpwo?timeout=10s)": context deadline exceeded
      
      {
          s: "kubectl -n e2e-jpwo-system apply -f config/samples/barjpwo_v1alpha1_foojpwo.yaml failed with error: (exit status 1) Error from server (InternalError): error when creating \"config/samples/barjpwo_v1alpha1_foojpwo.yaml\": Internal error occurred: failed calling webhook \"mfoojpwo.kb.io\": failed to call webhook: Post \"[https://e2e-jpwo-webhook-service.e2e-jpwo-system.svc:443/mutate-barjpwo-example-comjpwo-v1alpha1-foojpwo?timeout=10s](https://e2e-jpwo-webhook-service.e2e-jpwo-system.svc/mutate-barjpwo-example-comjpwo-v1alpha1-foojpwo?timeout=10s)\": context deadline exceeded\n",
      }

c/c @ibihim

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [camilamacedo86]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@camilamacedo86: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubebuilder-e2e-k8s-1-27-11	34af3f4	link	true	/test pull-kubebuilder-e2e-k8s-1-27-11
pull-kubebuilder-e2e-k8s-1-30-0	b44a3a8	link	true	/test pull-kubebuilder-e2e-k8s-1-30-0
pull-kubebuilder-e2e-k8s-1-28-7	b44a3a8	link	true	/test pull-kubebuilder-e2e-k8s-1-28-7
pull-kubebuilder-e2e-k8s-1-29-2	b44a3a8	link	true	/test pull-kubebuilder-e2e-k8s-1-29-2

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.