Add CI step to release workflow to check for semver hazards

[jdisanti]

This CI step will check for subtle semver hazards with the ConfigBag during release. Once all the runtime crates are independent, then this check can be moved into normal CI.

---

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
• No codegen difference in the Server Test Python
• No codegen difference in the Server Test Typescript

A new doc preview is ready to view.

[github-actions]

A new generated diff is ready to view.

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

A new doc preview is ready to view.

[jdisanti]

Ran a dry-run against this branch to confirm the new check works: https://github.com/smithy-lang/smithy-rs/actions/runs/7645480204/job/20832185070

[rcoh]

should note how to set this up (notably, $PWD/aws-sdk-rust, and smithy-rs need to exist)

[rcoh]

should we cargo check a few more?

[jdisanti]

I don't think cargo check will do a whole lot for us here since these breaks happen at runtime, unless you're thinking of having it detect backwards compatibility issues. These two services should compile enough runtime crates that I think it would catch most of those.

[rcoh]

have you tried creating an intentional semver break and then running release in preview mode?

[rcoh]

have you tried creating an intentional semver break and then running release in preview mode?

[jdisanti]

have you tried creating an intentional semver break and then running release in preview mode?

I verified that locally by invoking the script manually. I also confirmed the script is working correctly in GitHub Actions in https://github.com/smithy-lang/smithy-rs/actions/runs/7645370946/job/20831801559, where you can see it correctly picked up the patched crate version and then failed to compile due to deprecations and -D warnings (the latter of which I removed in a later revision of this PR):

   Compiling aws-sdk-s3 v1.13.0 (/home/build/workspace/aws-sdk-rust/sdk/s3)
error: use of deprecated type alias `aws_http::user_agent::AwsUserAgent`: Use aws_runtime::user_agent::AwsUserAgent instead.
 --> sdk/s3/tests/request_information_headers.rs:6:27
  |
6 | use aws_http::user_agent::AwsUserAgent;
  |                           ^^^^^^^^^^^^
  |
  = note: `-D deprecated` implied by `-D warnings`

error: use of deprecated type alias `aws_http::user_agent::AwsUserAgent`: Use aws_runtime::user_agent::AwsUserAgent instead.
  --> sdk/s3/tests/request_information_headers.rs:50:29
   |
50 |             layer.store_put(AwsUserAgent::for_tests());
   |                             ^^^^^^^^^^^^

error: use of deprecated constant `aws_http::content_encoding::header_value::AWS_CHUNKED`: Use aws_runtime::content_encoding::header_value::AWS_CHUNKED instead.
   --> sdk/s3/tests/checksums.rs:229:76
    |
229 |         HeaderValue::from_static(aws_http::content_encoding::header_value::AWS_CHUNKED),
    |                                                                            ^^^^^^^^^^^
    |
    = note: `-D deprecated` implied by `-D warnings`