Bump lambda_http dependency of aws-smithy-http-server to 0.8.0

[david-perez]

This patch also removes the unneeded dependency on lambda_runtime by
aws-smithy-http-server-python.

This patch also refactors LambdaHandler's convert_event to avoid
cloning the URI path when not needed.

This is a breaking change. See #2676 why.

This patch also bumps aws-smithy-http-server dependency on mime to 0.3.4.

cargo +nightly-2022-11-16 minimal-versions check --all-features otherwise
fails when using 0.3.0, because we require impl fmt::Display for mime::FromStrError, which was first introduced in 0.3.4.

As to why minimal-versions is now picking mime 0.3.0 with this patch, it's
because in lambda_http 0.7.3, they had mime = "0.3.16",
and in lambda_http 0.8.0, they've now relaxed that to mime = "0.3".

Checklist

• I have updated CHANGELOG.next.toml if I made changes to the smithy-rs codegen or runtime crates

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

A new generated diff is ready to view.

• No codegen difference in the AWS SDK
• No codegen difference in the Client Test
• No codegen difference in the Server Test
• Server Test Python (ignoring whitespace)
• No codegen difference in the Server Test Typescript

A new doc preview is ready to view.

[david-perez]

In CI, cargo +nightly-2022-11-16 minimal-versions check --all-features on aws-smithy-http-server fails with:

Checking mime v0.3.0
...
error[E0599]: the method `as_display` exists for reference `&FromStrError`, but its trait bounds were not satisfied
  --> aws-smithy-http-server/src/rejection.rs:18:13
   |
18 |     #[error("invalid `Content-Type` header value mime type: {0}")]
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ method cannot be called on `&FromStrError` due to unsatisfied trait bounds
   |
  ::: /opt/cargo/registry/src/github.aaakk.us.kg-1ecc6299db9ec823/mime-0.3.0/src/lib.rs:72:1
   |
72 | pub struct FromStrError {
   | ----------------------- doesn't satisfy `FromStrError: std::fmt::Display`
   |
   = note: the following trait bounds were not satisfied:
           `FromStrError: std::fmt::Display`
           which is required by `&FromStrError: DisplayAsDisplay`

Indeed, we require mime::FromStrError: std::fmt::Display, but said trait was first implemented in this commit, which first made its way out in mime 0.3.4. As to why minimal-versions is now picking mime 0.3.0 with this patch, it's because in lambda_http 0.7.3, they had mime = "0.3.16", and in lambda_http 0.8.0, they've now relaxed that to mime = "0.3".

I'll go ahead and bump the dependency of aws-smithy-http-server on mime to 0.3.4 and update the PR description.

[github-actions]

A new generated diff is ready to view.

• No codegen difference in the AWS SDK
• No codegen difference in the Client Test
• No codegen difference in the Server Test
• Server Test Python (ignoring whitespace)
• No codegen difference in the Server Test Typescript

A new doc preview is ready to view.