additional service specific protocol tests

[aajtodd]

Motivation and Context

There are several service specific http request/response tests from Smithy. These are similar to the protocol tests but apply only to a specific service. We were tasked with ensuring some of the S3 URI related tests were captured.

Description

We currently were running the API gateway related tests as part of the aws/sdk-adhoc-test package. There are also tests for machinelearning, glacier, and s3. I attempted to add all of these but hit issues.

1. machinelearning can be enabled but we have yet to actual implement the customization that would allow this test to pass.
2. s3 pulls in aws-config as a dev dependency for reasons and this causes conflicts between relocated and non-relocated runtime crates. The sdk-adhoc-test package does not implement any of the runtime relocation and Cargo.toml processing that the sdk build does (nor do I want to pursue that).

For now I've enabled the glacier tests and copied the S3 specific tests into s3-tests.smithy so that they are built and tested with the actual S3 model. In the future we can either (1) fix the build issues allowing us to remove these tests in favor of the ones defined in Smithy or (2) ideally these tests get implemented in the real upstream service models and we don't have to do anything special to get them.

Testing

Tested locally and 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.

• 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.

[ysaito1001]

This doesn't need to be copied to s3-tests.smithy either because it's already existing or irrelevant (just to better understand)?

[aajtodd]

This doesn't need to be copied to s3-tests.smithy either because it's already existing or irrelevant (just to better understand)?

These are all endpoint related tests that predate EP2.0. There should be EP2.0 tests in S3's model that cover these and more at this point.