Backport of Fix removed service-to-service peering links into release/1.16.x

[hc-github-team-consul-core]

Backport

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

🚨

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:
@trujillo-adam
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

In the PR #16291 the Mesh Gateway service-to-service peering page was removed (website/content/docs/connect/gateways/mesh-gateway/service-to-service-traffic-peers.mdx). Though it looks like not all links to that page were replaced. This PR tries to fix those occurrences.

I tried to find the best matching replacements to capture the intentions of the affected sections. Please feel free to suggest better alternatives and your raise concerns where you see fit. :)

Testing & Reproduction steps

1. Navigate to https://developer.hashicorp.com/consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-peers
2. 404 is presented

Links

Affected pages:

• https://developer.hashicorp.com/consul/docs/connect/gateways#mesh-gateways
• https://developer.hashicorp.com/consul/docs/connect/gateways/mesh-gateway
• https://developer.hashicorp.com/consul/docs/connect/gateways/mesh-gateway/peering-via-mesh-gateways
• https://developer.hashicorp.com/consul/docs/enterprise/admin-partitions
• https://developer.hashicorp.com/consul/docs/lambda/invoke-from-lambda

PR Checklist

• updated test coverage (n/a)
• external facing docs updated
• appropriate backport labels added
• not a security concern

---

Overview of commits

• 94e7b8a - 2f8939e - 0971635 - 9bc880c - 11934ea

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

2 out of 3 committers have signed the CLA.

• trujillo-adam
• karras
• temp

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

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

Auto approved Consul Bot automated PR