[Feature Request] Standardize operationIds to ensure uniqueness

We should consider standardizing the naming convention of operationIds to what we currently have in DevX API (PowerShell style) - https://github.com/microsoftgraph/microsoft-graph-devx-api/blob/dev/OpenAPIService/PowershellFormatter.cs? For example:

• Remove hash suffix values from operationIds for function all paths.
• Add '_' to separate verb (action) in an operationId. This typically the last . or second from last . for OData cast paths.
• PUT operations should have Set as the verb in an operationId {xxx}_Set{yyy}.

In PowerShell, we use operationIds to form command names.

As part of this exercise, we should add validation to ensure operationIds are unique for a given document.

Edit: This is a continuation of https://github.com/microsoft/OpenAPI.NET.OData/pull/338#discussion_r1097802458.

Inizia con il file referenziato OpenAPIService/PowershellFormatter.cs e la discussione collegata da pull request 338 per comprendere le convenzioni esistenti di operationId. Traccia dove vengono generati gli operationIds per i percorsi OData, quindi individua il punto di ingresso della convalida del documento; il lavoro è completato quando vengono applicate le regole di denominazione richieste e gli operationIds duplicati vengono rifiutati.