Bumps [h2](https://github.com/hyperium/h2) from 0.3.16 to 0.3.17.
- [Release notes](https://github.com/hyperium/h2/releases)
- [Changelog](https://github.com/hyperium/h2/blob/master/CHANGELOG.md)
- [Commits](hyperium/h2@v0.3.16...v0.3.17)

---
updated-dependencies:
- dependency-name: h2
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

This branch adds fields to the `OutboundPolicies` API messages for
configuring request timeouts. The `HttpRoute.Rule` and `GrpcRoute.Rule`
messages now contain a `requestTimeout` field, which contains a
`Duration` for a request timeout for that rule. In addition, the
`RouteBackend` messages also contain a `requestTimeout` field, which
configures a duration for requests dispatched to that specific backend.
All new fields have comments describing their intended semantics.

These fields are primarily intended to support the new timeout fields
added to the HTTPRoute CRD in GEP-1742 (see linkerd/linkerd2#10969). The
HTTPRoute timeout configuration are an additional field on the `rule`
fields in a route that contains optional `request` and `backendRequest`
timeouts. This means that a single request timeout and backend request
timeout is set for all backends on an individual route rule. 

The proxy API additions in this PR are somewhat more flexible than the
current HTTPRoute CRD, as each `RouteBackend` has its *own* field for
the `backendRequest` timeout. This means that in theory, independent
`backendRequest` timeout values could be configured for each individual
backend. HTTPRoute doesn't currently support this, but it felt like a
good idea to add this flexibility in the proxy API regardless, to
support future use cases.

## v0.10.0

* Add `requestTimeout` fields to routes and route backends in the
  `OutboundPolicies` API
* Rust: update `h2` to v0.3.17