[Feature] handle entity collection bound action/function correctly

[drivardxrm]

If a CustomApi (action/function) is bound to an Entity Collection, the entityId field is not relevant (needed).

The URL of this type of api must include the Entyset name and
Ex. {entitysetname}/Microsoft.Dynamics.CRM.{customapi_iniquename}

This PR forms proper URL for these type of CustomAPI when an entityName is provided but no entityId

ref. https://learn.microsoft.com/en-us/power-apps/developer/data-platform/custom-api

[Copilot]

Pull request overview

Updates Dataverse Web API execution URL construction to correctly support Custom APIs (actions/functions) bound to an entity collection, where entityId is not applicable. This aligns DataverseManager.execute() with Dataverse URL requirements for collection-bound operations.

Changes:

• Adjust URL building to treat entityName + missing entityId as an entity-collection-bound operation ({entitySetName}/Microsoft.Dynamics.CRM.{operationName}).
• Preserve existing behavior for record-bound operations ({entitySetName}({entityId})/...) and unbound operations.

[Power-Maverick]

@drivardxrm thanks for fixing this issue. Can you please resolve the PR comments so we can get this merged into dev