0.57 release tracking issue

[rcoh]

Tracking issue for release of 0.57 of smithy-rs

• Small tweaks to the HTTP wrapper #3099 (@rcoh)
• Use tokio::process to allow timeouts to occur #3052 (@rcoh)
• Move result and connection from aws-smithy-http to aws-smithy-types #3093 (@ysaito1001 )
• Feature-gate public use of http-body and hyper within aws-smithy-types #3088 (@ysaito1001 )
• Add more type aliases for types moved to the aws-smithy-types crate #3091 (@ysaito1001)
• Add Clone impl to PresignedRequest #3084 (@rcoh)
• Remove body 04x feature gating of read_from methods

Server:

• Allow custom writables in Instantiator #3104 (@david-perez)
• Build services with a derived configuration object #3095 (@82marbag)

[david-perez]

I need to merge #3095, but it won't need any changes to runtime crates.

[david-perez]

Generated server SDKs re-export SdkBody and ByteStream in types.rs:

pub use ::aws_smithy_types::body::SdkBody;
pub use ::aws_smithy_types::byte_stream::error::Error as ByteStreamError;
pub use ::aws_smithy_types::byte_stream::AggregatedBytes;
pub use ::aws_smithy_types::byte_stream::ByteStream;
pub use ::aws_smithy_types::date_time::Format as DateTimeFormat;
pub use ::aws_smithy_types::error::display::DisplayErrorContext;
pub use ::aws_smithy_types::Blob;
pub use ::aws_smithy_types::DateTime;

I guess that we need to expose similarly named feature flags as the ones in #3088 to toggle exposure of the feature-gated methods in aws-smithy-types? cc @drganjoo.

[rcoh]

probably not critical since we aren't as worried about compatibility and the server is always going to be HTTP. It's more about forward-looking work to support not-Http things, allow a seamless upgrade to http-body = 1, etc.

[rcoh]

All required PRs are merged, release is in progress