Fix/528 Use fields from parent - Create Collection form behavior

[g-saracca]

What this PR does / why we need it:

In the Create Collection form, when the user checks the “Use fields from [parent]” checkbox, we are now sending metadata block names and input levels as undefined to the js-dataverse use case.
This was tested also using the GHCR container image generated from IQSS/dataverse#10985 PR and it works great.

This comment from @pdurbin explains what this is fixing very well.

Which issue(s) this PR closes:

• Closes Create Collection - if "Use metadata fields from [Parent]" is checked, send blocknames & input levels as undefined #539

Suggestions on how to test this:

Step 1: Run the Development Environment

1. Execute npm i.
2. Navigate with cd packages/design-system && npm i && npm run build.
3. Return with cd ../../.
4. Ensure you have a .env file similar to .env.example, with the variable VITE_DATAVERSE_BACKEND_URL=http://localhost:8000.
5. Navigate with cd dev-env.
6. Start the environment using ./run-env.sh unstable.
7. To verify the environment, visit http://localhost:8000 and check your local Dataverse installation.

Step 2: Test the fix

1. Create a collection called "One", but not using fields from Root, select an extra metadata block.
2. Create another collection called "One child" within the "One" collection, leave the "Use fields from One" checked.
3. Navigate to create a collection within "One child" and check that in the metadata fields section the default metadata blocks checked are the same from collection "One", its not necessary to create another collection here.
4. Go to the JSF version and edit the metadata blocks from collection "One" (edit collection is not yet supported in the SPA).
5. Go to the "One child" collection within the SPA, navigate to create a collection in it and verify now that in the metadata fields section, the default metadata blocks checked are now the same from collection "One", its also not necessary to create another collection here.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

No

Is there a release notes update needed for this change?:

No

Additional documentation:

No

[coveralls]

coverage: 97.574% (+0.2%) from 97.388%
when pulling 355afad on fix/528-use-fields-from-parent-form-behavior
into 110d696 on develop.

[ekraffmiller]

This change is causing an error in Create Dataset, when the parent collection is not the Root. We need a fix in the Dataverse API to get the correct metadata fields for the Create Dataset form. Added a waiting tag to this issue.
Here is the error:

createDatasetTest.mov

[g-saracca]

@ekraffmiller working great on my end after pulling new unstable dataverse image.

Screen.Recording.2024-11-05.at.14.49.43.mov

[ekraffmiller]

@ekraffmiller working great on my end after pulling new unstable dataverse image.

Screen.Recording.2024-11-05.at.14.49.43.mov

Working for me now too, needed to get the newest image

[ekraffmiller]

looks good, approving 👍

[ofahimIQSS]

No issues found during testing. Merging PR.
Uploading Testing of 540.docx…