Use the endpoint operation for client endpoin tests if exists

[dagnir]

Motivation and Context

If the service uses endpoint discovery, default to the service's endpoint operation, otherwise we risk picking an operation that relies on endpoint discovery, in which case the client endpoint tests will be useless because we skip using the Endpoints 2.0 endpoint provider if we have an endpoint from Endpoint Discovery.

Modifications

Use the endpoint operation by default for client endpoint tests if the service has one.

Testing

mvn clean install

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]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

77.8% Coverage
0.0% Duplication