Backport of docs: Consul DNS views on Kubernetes into release/1.20.x

[hc-github-team-consul-core]

Backport

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

🚨

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:
@boruszak
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: POST https://api.github.com/repos/hashicorp/consul/merges: 409 Merge conflict []

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

---

Description

This PR updates the Consul v1.20 documentation to support the Consul DNS proxy on Kubernetes deployments.

Links

PR Checklist

• updated test coverage
• external facing docs updated
• appropriate backport labels added
• not a security concern

---

Overview of commits

• 55db870 - 418a32f - 63e4511 - 280f6d3 - 1f45e86 - af1c0ea - 026bcce - f283575 - 18bda48 - 069e8c5 - 37217e9 - 438feb3 - 890153a - f16f185 - 14ac75b - ab21dff - 1df1759 - 99e1e3e - 993d7a4 - 701f1b9 - 98dfacd - 752dbf2 - e742b72

[github-team-consul-core-pr-approver]

Auto approved Consul Bot automated PR

[zalimeni]

@boruszak I don't think the commit that was merged is correct- this backport failed, and the contents of the commit are blank (it's an unrelated commit that was already backported - I think it came into your original PR bc of merging main into the PR but not squashing). Checking https://github.com/hashicorp/consul/blob/release/1.20.x/website/content/docs/k8s/dns/views/enable.mdx (1.20.x) I don't see the docs

I think we'll need to manually backport that PR to release/1.20.x