Check schemes match for SignerProperties in SRA client

[gosar]

Motivation and Context

This is to address an issue from an earlier PR #4495 (comment). The change was made earlier to account for useSraAuth=false, but affects an edge-case for useSraAuth=true.

Modifications

Added the removed check back, but made it conditional on useSraAuth=true.

Testing

I think a functional test could be added to codegen-generated-classes-test to show the issue and prevent it from reoccurring in future. Might have to come back to adding test later, based on prioritization.

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
474 Code Smells

84.3% Coverage
3.9% Duplication

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