Network policy to allow connection to k8s API service

[leochr]

Create an egress network policy to allow the LTPA Job to access the k8s API service (kubernetes.default.svc).

Service address can't be referred in network policies. Instead look up the IP address of the API service and use it instead. Operator pod should be injected with the service details as an env variable

[kabicin]

Fix is ready for review for WLO WASdev/websphere-liberty-operator#615, if that looks good I can also port the changes to OLO.

[kabicin]

Rebased onto main and fixed small issue with the bundle.
WLO: WASdev/websphere-liberty-operator#615
OLO: #573
Tests: https://github.ibm.com/websphere/operators/pull/123

[leochr]

@kabicin Now that the LTPA Job is no longer needed, please revisit this when you get a chance. Thank you.

[kabicin]

RCO: application-stacks/runtime-component-operator#708
OLO: #731
WLO: WASdev/websphere-liberty-operator#768
Tests: https://github.ibm.com/websphere/operators/pull/240

When I took a look the operator pod injected with service details did not make sense at the moment because it could be applied at runtime when possibly being used under a deny all egress, and the request to kube apiserver may not go through. Instead, I was thinking we could apply a permissive Egress on the operator during install (keeping constant for all install methods when pre-generating manifests), then modify the Egress at runtime for the operator to harden the network (such as based on ENV as mentioned above).

It seems network policy scaffolding was added in v1.39.0 which makes me think we should revisit at a later time so that we can mirror their structured project layout. https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.39.0/.