Update generated code

[async-aws-bot]

The AWS API contract changed with version 3.288.1.

This PR contains the new definition for Services.

[stof]

Tests are failing because the Sqs client has migrated to the JSON format instead of the XML format.

For unit tests, it requires updating the tests to expect JSON format
For integration tests, it requires replacing the asyncaws/testing-sqs docker image with an image supporting the JSON format.

and the code generator also has a bug (which is why static analysis fails and is also triggered in some tests)

[GrahamCampbell]

Probably we should also bump the major version, since the exceptions have changed.

[stof]

AFAICT, we only have much more cases that have dedicated exceptions instead of the generic ClientException. As the specific exceptions extend ClientException, I'm not sure it is actually a BC break.

[GrahamCampbell]

$name not $mapKey.

[stof]

the bot will not automatically fix bugs in the code generator by reading review comments...

[stof]

however, it might make sense to still make it a major version of that service in case some people use alternate implementations of SQS (in local setups for instance) which might not support the json format (which is basically what our own testsuite does)

[stof]

For reference, the official AWS SDK released the switch to the JSON protocol in a patch release (3.285.2), not even in a minor release.

[GrahamCampbell]

I guess we need to skip the localstack sqs tests for now?

[GrahamCampbell]

Probably we should just re-gen the baseline file for those psalm issues.

[stof]

For the integration tests, we could indeed skip them until #1596 is done and then localstack is used for the SQS integration tests instead of our custom unmaintained image (that does not support json). This will actually also need to wait for localstack to support the json protocol, which is in-progress
For unit tests, we need to update them.
For Psalm, we should indeed put them in the baseline. That's our usual errors for enum fields in json-based services (not sure why we don't have the similar issue for query-based services)

[stof]

I started the work of updating the testsuite for this.

[jderusse]

PR to add support to LocalStack has just been merged localstack/localstack#8268 a new version should be tagged soon

[stof]

@jderusse but updating localstack in #1596 is currently stuck because it has a bug that impacts our CI (which made us pin an old release years ago, but unfortunately without reporting it upstream at that time). So for now, I'll just skip those tests.

[jderusse]

ok... I was wrong. SQS test suite used https://github.com/async-aws/testing-sqs (an not localstack)
If I'm not wrong, this container is also used by Symfony to test messenger's bridge.

I've temporary disabled the tests to unlock this situation (this PR become bigger and bigger everyday)

[stof]

I'm merging this so that the bot does not override the manual fixes tomorrow morning.