Backport of docs: JWT auth docs display fixes into release/1.16.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #17765 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: "7a874f374b61fdf3d03ea790ed41511403d3fe88", automatic backport requires rebase workflow

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

---

Description

An error in merging and backporting for the v1.16 release caused part of the JWT Auth docs to be merged into main but not into the release/1.16.x branch. As a result, the page is not displaying properly in the live docs.

This PR re-applies those commits to merge into the 1.16 release branch.

PR Checklist

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

---

Overview of commits

• 5ad349c - 7a874f3 - e4da0a4 - 3873cb4 - 149f4d4

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

Auto approved Consul Bot automated PR

[jmurret]

This was already there when the 1.16.x branch was cut. Here is an example: https://github.com/hashicorp/consul/blame/release/1.16.x/website/content/docs/connect/config-entries/jwt-provider.mdx#L1033