Backport of docs: document behaviour of tls.https.verify_outgoing into release/1.14.x

[hc-github-team-consul-core]

Backport

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

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

---

At first it's not clear what verify_outgoing would do for the https listener as it seems like Consul agent's don't make https requests. Upon further investigation, it's clear that Consul agents do make https requests in the following scenarios:

• to implement watches
• to perform checks

In the first scenario, this setting is used here:

consul/agent/config/runtime.go

Line 1725 in a1c8d4d

func (c *RuntimeConfig) APIConfig(includeClientCerts bool) (*api.Config, error) {

In the second scenario, it's actually the internal_rpc setting that is used:

consul/tlsutil/config.go

Line 903 in a1c8d4d

config := c.internalRPCTLSConfig(false)

---

Overview of commits

• ded3c9f - f6ce7c3

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

Auto approved Consul Bot automated PR

[hc-github-team-consul-core]

🤔 This PR has changes in the website/ directory but does not have a type/docs-cherrypick label. If the changes are for the next version, this can be ignored. If they are updates to current docs, attach the label to auto cherrypick to the stable-website branch after merging.

[lkysow]

Closing because the Go tests are broken due to changes in how we lint retries but not worth trying to backport all those changes to 1.14 just to get a 1 line docs PR in to those old docs.