Duplicate operation ids for functions overloads

[baywet]

OData functions with overloads get the same operationId resulting in an invalid OpenAPI document.
Functions should contain their parameters in the OperationId so they don't collide.

Assemblies affected

1.4.0

Steps to reproduce

Convert Graph v1. As additionalAccess function has multiple overloads, we get colliding operation ids, which is invalid for OpenAPI.

Expected result

Functions overloads to have different operation ids

Actual result

• /identityGovernance/entitlementManagement/assignments/additionalAccess(accessPackageId=''{accessPackageId}'',incompatibleAccessPackageId=''{incompatibleAccessPackageId}'')
• /identityGovernance/entitlementManagement/assignments/additionalAccess()

Both have the same operation id of identityGovernance.entitlementManagement.assignments.additionalAccess

Additional detail

Related #382 #324 microsoftgraph/msgraph-metadata#289 APIs-guru/openapi-directory#1053

[irvinesunday]

The initial implementation was set up to append a hash suffix to the operation ids in cases of overloaded functions, for example

/identityGovernance/entitlementManagement/assignments/microsoft.graph.additionalAccess():
    description: Provides operations to call the additionalAccess method.
    get:
      tags:
        - identityGovernance.Functions
      summary: Invoke function additionalAccess
      operationId: identityGovernance.entitlementManagement.assignments.additionalAccess-1164

The above implementation needs to be updated to be able to read BindingParameter types of collection.