Update hyper requirement from 0.14 to 1.3

[dependabot[bot]]

Updates the requirements on hyper to permit the latest version.

Release notes

Sourced from hyper's releases.

v1.3.1

Bug Fixes

• client: revert auto content-length header for some requests (#3633)

Changelog

Sourced from hyper's changelog.

v1.3.1 (2024-04-16)

Bug Fixes

• client: revert auto content-length header for some requests (#3633)

v1.3.0 (2024-04-15)

Bug Fixes

• client: send content-length even with no body (172fdfaf)
• http2:
  • max_header_list_size(num) defaults to 16kb (203d1b09)
  • initial_max_send_streams defaults to 100 (2d1bd708)
• server:
  • avoid unwrapping for the Future impl of HTTP/1 UpgradeableConnection (#3627) (b79be911, closes #3621)
  • avoid graceful_shutdown panic on upgraded H1 connection (#3616) (6ecf8521)

Features

• client:
  • add max_header_list_size(num) to http2::Builder. (1c5b1b87)
  • add max_pending_accept_reset_streams HTTP2 option (#3617) (330ddf1d)
• ext: implement From ReasonPhrase for Bytes (dc27043a)
• service: expose Service and HttpService trait unconditionally (6aee2e6e)
• server: relax 'static from connection IO trait bounds (#3595) (0013bdda)

v1.2.0 (2024-02-21)

Bug Fixes

• http2: typo in trace logging (#3536) (79862ec2)
• rt: Sleep::downcast_mut_pin() no longer extend lifetime (7206fe30, closes #3556)

Features

• http1: support configurable max_headers(num) to client and server (#3523) (b1142448)
• http2:
  • add config for max_local_error_reset_streams in server (#3530) (d7680e30)
  • add initial_max_send_streams method to HTTP/2 client builder (#3524) (fdfa60d9)
  • add max_pending_accept_reset_streams(num) back to HTTP/2 server builder (#3507 (a9fa893f)

Breaking Changes

... (truncated)

Commits

• c78379e v1.3.1
• 3705a7e Revert "fix(client): send content-length even with no body"
• d53305a v1.3.0
• dc27043 feat(ext): implement From ReasonPhrase for Bytes
• 6aee2e6 feat(service): expose Service and HttpService trait unconditionally
• 172fdfa fix(client): send content-length even with no body
• b79be91 fix(server): avoid unwrapping for the Future impl of HTTP/1 `UpgradeableCon...
• 203d1b0 fix(http2): max_header_list_size(num) defaults to 16kb
• 1c5b1b8 feat(client): add max_header_list_size(num) to http2::Builder.
• df33d4d refactor(h1): use UninitSlice::as_uninit_slice_mut() instead of cast (#3618)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changelog-app[bot]]

Generate changelog in changelog-dir>`changelog/@unreleased`</changelog-dir

What do the change types mean?

- `feature`: A new feature of the service. - `improvement`: An incremental improvement in the functionality or operation of the service. - `fix`: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way. - `break`: Has the potential to break consumers of this service's API, inclusive of both Palantir services and external consumers of the service's API (e.g. customer-written software or integrations). - `deprecation`: Advertises the intention to remove service functionality without any change to the operation of the service itself. - `manualTask`: Requires the possibility of manual intervention (running a script, eyeballing configuration, performing database surgery, ...) at the time of upgrade for it to succeed. - `migration`: A fully automatic upgrade migration task with no engineer input required. _Note: only one type should be chosen._

How are new versions calculated?

- ❗The `break` and `manual task` changelog types will result in a major release! - 🐛 The `fix` changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease. - ✨ All others will result in a minor version release.

Type

- [ ] Feature - [ ] Improvement - [ ] Fix - [ ] Break - [ ] Deprecation - [ ] Manual task - [ ] Migration

Description

Update hyper requirement from 0.14 to 1.3 **Check the box to generate changelog(s)** - [ ] Generate changelog entry

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.