chore(deps): update rust crate http to v1

[renovate[bot]]

This PR contains the following updates:

Package	Type	Update	Change
http	workspace.dependencies	major	0.2.11 -> 1.0.0

---

Release Notes

hyperium/http (http)

v1.1.0

Compare Source

• Add methods to allow trying to allocate in the HeaderMap, returning an error if oversize instead of panicking.
• Add Extensions::get_or_insert() method.
• Implement From<Uri> for uri::Builder.
• Fix HeaderName::from_lowercase that could allow NUL bytes in some cases.

v1.0.0

Compare Source

• Implement Clone for Request, Response, and Extensions. This breaking change requires that all extensions now implement Clone.
• Add a default-on std feature. Disabling it currently is not supported.
• Fix MIRI warnings in HeaderMap::iter().

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions[bot]]

@renovate[bot], please consider creating a changeset entry in /.changesets/. These instructions describe the process and tooling.

[router-perf[bot]]

CI performance tests

• [ ] events_big_cap_high_rate - Stress test for events with a lot of users, deduplication enabled and high rate event with a big queue capacity
• [ ] events_without_dedup - Stress test for events with a lot of users and deduplication DISABLED
• [ ] events - Stress test for events with a lot of users and deduplication ENABLED
• [ ] large-request - Stress test with a 1 MB request payload
• [x] step - Basic stress test that steps up the number of users over time
• [ ] xlarge-request - Stress test with 10 MB request payload
• [ ] reload - Reload test over a long period of time at a constant rate of users
• [ ] no-graphos - Basic stress test, no GraphOS.
• [ ] events_callback - Stress test for events with a lot of users and deduplication ENABLED in callback mode
• [ ] xxlarge-request - Stress test with 100 MB request payload
• [ ] step-jemalloc-tuning - Clone of the basic stress test for jemalloc tuning
• [ ] events_without_dedup_callback - Stress test for events with a lot of users and deduplication DISABLED using callback mode
• [x] const - Basic stress test that runs with a constant number of users
• [ ] events_big_cap_high_rate_callback - Stress test for events with a lot of users, deduplication enabled and high rate event with a big queue capacity using callback mode

[renovate[bot]]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 1.1.0
    Updating crates.io index
error: failed to select a version for the requirement `http = "^0.2"`
candidate versions found which didn't match: 1.1.0
location searched: crates.io index
required by package `add-timestamp-header v0.1.0 (/tmp/renovate/repos/github/apollographql/router/examples/add-timestamp-header/rhai)`
perhaps a crate was updated and forgotten to be re-vendored?

[renovate[bot]]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 1.1.0
    Updating crates.io index
error: failed to select a version for the requirement `http = "^0.2"`
candidate versions found which didn't match: 1.1.0
location searched: crates.io index
required by package `add-timestamp-header v0.1.0 (/tmp/renovate/repos/github/apollographql/router/examples/add-timestamp-header/rhai)`
perhaps a crate was updated and forgotten to be re-vendored?