Generate client endpoint tests if test cases have operationInputs or otherwise are viable

[cenedhryn]

to ignore test cases that lack operationInputs unless explicitly instructed to include them

Motivation and Context

The generated client endpoint tests aim to provide a more comprehensive e2e test coverage for endpoint rules than the tests that target the resolver itself. However, the client level tests require input parameters in order to work (calling an API).
Prior to this change, we always included all test cases in the generated client endpoint tests independently of whether the test case had the operationInput member or not, and manually added test cases that didn't work to the test skip list. When new tests are added, it requires manual intervention and an increased ops load.

With this change, we only generate tests for the test cases with operationInputs, unless an overriding flag is set. The override flag should be used for services where the codegen can find suitable input parameters without relying on operationInputs, such as endpoint prefix enabled services.

Modifications

• Removes auto-codegen of client tests when operationInput is missing
• If there are no tests at all, do not generate the class
• Adds a flag generateEndpointClientTests that overrides the operationInput condition
• Adds the new flag to the customization.config of 13 services with hostPrefix
• Removes unnecessary test skips for the 5 services that explicitly excluded tests of the type missing operation input

Testing

The tests for this PR should pass before approval

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.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

51.5% Coverage
16.4% Duplication