Backport of [NET-10961] Ignore gke managed namespaces by default into release/1.3.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #4333 to be assessed for backporting due to the inclusion of the label backport/1.3.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@NiniOak
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: unable to process merge commit: "0aaf003e3c05372cdc360d347638849949623366", automatic backport requires rebase workflow

The below text is copied from the body of the original PR.

---

Changes proposed in this PR

• on GKE we should not attempt to inject pods in a gke managed namespaces because many of them do not have a corresponding k8s service which causes the connect injector container to crash and send those pods into an infinite crash loop

How I've tested this PR

• deployed gke cluster with consul using this helm chart update, the containers in the gke managed namespaces were no longer crashing after this change

How I expect reviewers to test this PR

Follow the instructions in the README for this repo: https://github.com/jm96441n/consul-experiments/tree/main/k8s/gke-ns

Checklist

• Tests added
• CHANGELOG entry added

---

Overview of commits

• 79f171b - 7d2782e - 0aaf003 - 6fb774b