Backport of docs: Failover overview minor fix into release/1.16.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #17743 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:
@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: unable to process merge commit: "2ffa0a819148d8c8e1de6fdfa7e3789bc26f6525", automatic backport requires rebase workflow

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

---

Description

I noticed a typo when looking at the failover docs. According to the table, prepared queries support cluster peering. That is incorrect - prepared queries require a primary datacenter. Hence the point of the table - to show the distributed use cases.

It was surely a copy and paste typo - so this PR fixes it!

PR Checklist

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

---

Overview of commits

• a459c19 - 2ffa0a8 - 9fa1569 - 1790d7e - d60ec86

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

Auto approved Consul Bot automated PR