DatasetValidator allow empty fields for conditionally required fields.

[g-saracca]

What this PR does / why we need it:

Modifies the Create/Update Dataset Validator to allow empty values in child fields that are required but their parent fields (compound fields) are not.
These child fields should only be truly required when one of their siblings fields has a value; otherwise, they can be left empty.

I have also added a new parameter to the UpdateDataset use case which is the internalVersionNumber of the dataset, and also now in the GetDataset use case we are returning that property to be used later.
Integration tests were added 👍🏼 .

• @param {number} [internalVersionNumber] - The internal version number of the dataset. If another user updates the dataset version metadata before you send the update request, data inconsistencies may occur. To prevent this, you can use the optional internalVersionNumber parameter. This parameter must include the internal version number corresponding to the dataset version being updated. Note that internal version numbers increase sequentially with each version update.

Which issue(s) this PR closes:

• Closes DatasetValidator allow empty fields for conditionally required fields. #272

Related Dataverse PRs:

• Depends on Edit Metadata API endpoint - support empty values dataverse#11273

Suggestions on how to test this:

review code and unit tests

[ChengShi-1]

Good job! Just 2 small things.

1. I notice the internalVersion is an optional parameter from api, but it is set to be required in modal dataset.ts and datasetPayload.
2. Some comments left here, not sure if you want them to be a guidance, or you want to remove them. If it is meant to be there, just ignore my comments there.

[ChengShi-1]

Great

[ofahimIQSS]

Tests are passing, merging