Backport of Add ServiceResolver RequestTimeout for route timeouts to make TerminatingGateway upstream timeouts configurable into release/1.15.x

[hc-github-team-consul-core]

Backport

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

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

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

I'm not entirely sure about this approach because it's unclear to me where we generally use ConnectTimeout for ServiceResolvers and whether or not this is conflating two timeout values that shouldn't be conflated. If so, I can add another timeout value that makes this configurable. Edit: Adding a RequestTimeout parameter for ServiceResolvers to handle the timeout. That said, this change allows for overriding Envoy's default timeout for establishing connections to upstream clusters in a route configuration.

I tested it manually with a custom go binary run on the mesh with a TerminatingGateway and ServiceResolver that extends the timeout to 30 seconds so that a server that takes 20 seconds to respond doesn't timeout. I'll be adding some sort of integration test, but wanted to open this to get eyes on the approach first.

Note that two changes are necessary for this to work with terminating gateways, the first is to allow the local proxy that a service uses to route traffic through the mesh to configure the timeout for its routes via makeUpstreamRouteForDiscoveryChain, the second is to have the TerminatingGateway itself configure its routing timeouts via makeNamedDefaultRouteWithLB.

Testing & Reproduction steps

The files I used to manually validate are here. I compiled main.go as timeout-check, copied it to the root of the consul directory and locally compiled consul. I then booted up Consul, ran the timeout-check.sh script and issued a curl to localhost:9877 to kick off a request through the service mesh to the external sleeping service. Without this change I see:

➜  ~ curl localhost:9877
upstream request timeout%

With it I see:

➜  ~ curl localhost:9877
finished%

PR Checklist

• updated test coverage
• external facing docs updated
• not a security concern

---

Overview of commits

• 29768f2 - 1f26c2a - 0fae217 - de49222

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

Auto approved Consul Bot automated PR

[andrewstucki]

Slight diff drift from having to regenerate the proto files from a merge conflict.