chore: Set Custom Operation ID for ApiOperation Annotations

[manuraf]

List of Changes

• Updated ApiOperation annotations that has changed to include a custom operationId.
• Ensured that these endpoint has a previous operationId to prevent naming conflicts and ensure smooth updates on APIM.

Motivation and Context

This pull request introduces a custom operationId within the ApiOperation annotations to ensure consistent updates of our APIs on Azure API Management (APIM). The custom operationId is crucial to avoid issues that arise when the operationId changes, which can prevent the API from updating correctly. Without a custom operationId, renaming an operationId necessitates deleting and recreating the entire API group, leading to temporary service disruptions and loss of analytics data.

How Has This Been Tested?

Screenshots (if appropriate):

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud