Add useSraAuth to switch codegen for clients

[gosar]

Motivation and Context

This follows up from #4471 where old Signer was brought back, meaning clients were configured with both pre-SRA old Signer and SRA auth scheme resolution. With this change, adding a customization flag that codegen logic switches on to generate either old/new approach.

Modifications

• Add customization flag
• Update different codegen classes to switch as needed
  • Note, this doesn't add switching logic for newly added codegen changes for plugins - Add missing properties and polish the codegen path #4458. We may be able to do this later, if we have time, but I think it is ok to generate the plugin interfaces, they just won't be supported until we release that service with SRA.
  • To support the plugin interfaces, other SRA interfaces like AuthSchemeProvider need to also be codegenerated. So leaving all the tasks in https://github.com/aws/aws-sdk-java-v2/blob/feature/master/sra-identity-auth/codegen/src/main/java/software/amazon/awssdk/codegen/emitters/tasks/AuthSchemeGeneratorTasks.java#L40 around. Generating additional classes for some time that aren't used until we switch the service to SRA sounds ok and simplifies the work now.
• No AWS services are switched to useSraAuth=true, so everything will generate pre-SRA, which is what we want at the start of the release.
• For now, switched the minimum services in codegen-generated-classes-test to useSraAuth=true to make sure all tests pass. TODO: There is actually more codegen switching logic needed (related to EndpointResolutionInterceptor changes from Remove legacy endpoint auth scheme logic and add putAuthScheme to AWS client builder. #4311) to make these tests work with useSraAuth=false.
• TODO: switch all codegen-generated-classes-test services to useSraAuth=true, so we fully test new approach.
• update: switched s3,s3control too, to useSraAuth=true to make the tests pass. Again related to Remove legacy endpoint auth scheme logic and add putAuthScheme to AWS client builder. #4311

Testing

see points above

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

SonarCloud Quality Gate failed.   

4 Bugs
0 Vulnerabilities
2 Security Hotspots
448 Code Smells

84.4% Coverage
3.9% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint