feat: exclude controller to admin comms from mesh

[rainest]

What this PR does / why we need it:

Set Kuma and Istio outbound traffic excludes

Which issue this PR fixes

Part of Kong/kubernetes-ingress-controller#4698

Special notes for your reviewer:

See Kong/kubernetes-ingress-controller#4698 (comment) re design. The ingress chart subchart usage prevents us from automating the annotation value cleanly. It's unlikely it would need to change (we do expose the admin port configuration, but I don't know a reason you'd ever change it), but setting it in ingress's values.yaml runs the risk of accidentally excluding new annotations added in the kong chart values.yaml.

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• PR is based off the current tip of the main branch.
• Changes are documented under the "Unreleased" header in CHANGELOG.md
• New or modified sections of values.yaml are documented in the README.md ingress doesn't really use it?
• Commits follow the Kong commit message guidelines

[pmalek]

@rainest Can you elaborate what you mean by:

The ingress chart subchart usage prevents us from automating the annotation value cleanly

?

[pmalek]

I guess this is the answer: Kong/kubernetes-ingress-controller#4698 (comment)