Codegen changes for AuthSchemeInterceptorSpecs to update the RegionSet from Execution Attributes

[joviegas]

Motivation and Context

• Modify interceptor to update the RegionSet from Execution Attributes
• Fall back region is always configured Region if no RegionSet configured on Client (Requirement doc)
  (Note Will raise a separate PR later for EndpointBased Auth case that is legacy service like SES , S3 etc)

Modifications

Generated Code looks like below

    private MultiauthAuthSchemeParams authSchemeParams(SdkRequest request, ExecutionAttributes executionAttributes) {
        String operation = executionAttributes.getAttribute(SdkExecutionAttribute.OPERATION_NAME);
        MultiauthAuthSchemeParams.Builder builder = MultiauthAuthSchemeParams.builder().operation(operation);
        Region region = executionAttributes.getAttribute(AwsExecutionAttribute.AWS_REGION);
        builder.region(region);
        // Comment on PR : This code is generate only if Service has Sigv4a Auth
        RegionSet regionSet = executionAttributes.getOptionalAttribute(AwsExecutionAttribute.AWS_SIGV4A_SIGNING_REGION_SET)
                .filter(regions -> !regions.isEmpty()).map(regions -> RegionSet.create(String.join(", ", regions)))
                .orElseGet(() -> {
                    Region fallbackRegion = executionAttributes.getAttribute(AwsExecutionAttribute.AWS_REGION);
                    return fallbackRegion != null ? RegionSet.create(fallbackRegion.toString()) : null;
                });
        ;
        builder.regionSet(regionSet);
        return builder.build();

Testing

• Junits added for codegen
• Junits for interceptors to check AuthScheme Params are updated

Screenshots (if appropriate)

License

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

[joviegas]

This part is needed because earlier Builder was built in a single line
Since we have conditional bases builder for sigv4a so splited this generation code

QueryAuthSchemeParams.builder().operation(operation).region(region).build();

[sonarqubecloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
96.6% Coverage on New Code
1.4% Duplication on New Code

See analysis details on SonarQube Cloud

[zoewangg]

Discussed offline, we should consider removing useMultiAuth

[joviegas]

Added JAVA-8023 and also added in planning