Dataverse trigger metadata omits required dataset and table parameters

[daviburg]

Problem

The generated Dataverse trigger parameter metadata for CommondataserviceTriggerOperations.OnNewItems exposes only $filter, $orderby, $top, and $skip.

Live Connector Namespace TriggerConfig creation for GetOnNewItems_V2 rejects the request unless both dataset and table are supplied:

1. Without dataset: OpenApiOperationParameterValidationFailed - missing required property dataset.
2. With dataset but without table: OpenApiOperationParameterValidationFailed - missing required property table.
3. With both values returned by Dataverse discovery: TriggerConfig creation succeeds with 201 Created and state: Enabled; a new account invokes the configured callback.

Expected

CommondataserviceTriggerParameters.OnNewItems should expose the required trigger configuration fields so callers can construct a valid TriggerConfig from generated metadata. The same contract should be reviewed for OnDeletedItems and OnUpdatedItems.

Acceptance criteria

• Add dataset and table constants to the generated parameter metadata for each applicable Dataverse row trigger.
• Mark required versus optional parameters accurately in the generator source/model if that metadata surface supports it.
• Add regression coverage for the generated trigger parameter set.
• Regenerate the Dataverse client and verify a TriggerConfig payload can include all required fields without undocumented string literals.