Backport of [Security] SECVULN-8621: Fix XSS Vulnerability where content-type header wasn't explicitly set in API requests into release/1.20.x

[hc-github-team-consul-core]

Backport

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

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

---

Description

• Modified existing ensureContentTypeHeader middleware to set the response Content-Type to match the type of content that the server will process.

SOLUTION

ensureContentTypeHeader middleware is used to determine if the content-type set in the API request is the expected content type. If it's not a match:

• A warning is logged in Consul
• The appropriate contentType Header set before processing the request.
• The same action is carried out for API response.
  NOTE: The same function is used in doRequest function which is used in processing CLI requests to the Consul API.

Testing & Reproduction steps

Updated unit tests to add additional checks for content-type header
Vercel should deploy UI with no errors

MANUAL TESTING

Before Changes

After Changes

PR Checklist

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

---

Overview of commits

• c76765b - 01a6157

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

Auto approved Consul Bot automated PR