What this PR does / why we need it:

Modifies how we are sending the DTO while creating or updating a collection

Which issue(s) this PR closes:

• Closes Modify DTO sent to CreateCollection and UpdateCollection use cases - SPA frontend #593

Special notes for your reviewer:

Please first Review and QA the JS-dataverse related PR IQSS/dataverse-client-javascript#250, once is merged I will update the js-dataverse package used in this PR and it will be ready for QA.

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 feature
In the SPA, edit the root collection, change any field, everything should be updated correctly.
Smoke test creating and updating sub collections could be nice also.