206 - Integration dataset locks

[MellyGray]

What this PR does / why we need it:

This PR adds the integration of the SPA with the js-dataverse implementation to get the dataset locks.

Which issue(s) this PR closes:

• Closes Integration - Get dataset locks #206

Special notes for your reviewer:

I didn't add an e2e test because the integration + unit tests seemed enough.

Suggestions on how to test this:

Step 1: Run the development environment

1. Run npm I
2. cd packages/design-system && npm run build
3. cd ../../
4. Check that you have a .env file such as the .env.example, with the VITE_DATAVERSE_BACKEND_URL=http://localhost:8000 variable
5. cd dev-env
6. ./run-env.sh unstable
7. To check the environment go to http://localhost:8000 and check your local dataverse installation

Step 2: Test Dataset View mode with the implemented changes

1. Go to http://localhost:8000
2. Login as admin using username: dataverseAdmin and password: admin1
3. Create a new Dataset
4. Force a publication lock in the dataset using curl -H "X-Dataverse-key: $API_TOKEN" -X POST "$SERVER_URL/api/datasets/$ID/lock/finalizePublication" Check docs
5. From the dataset view mode copy the search parameters from the url. Ex.: ?persistentId=doi:10.5072/FK2/LHGRHP&version=DRAFT
6. Go to http://localhost:8000/spa/datasets and paste the search parameters. Ex.: http://localhost:8000/spa/datasets?persistentId=doi:10.5072/FK2/LHGRHP&version=DRAFT
7. You are seeing now the same Dataset in the SPA. Check that the buttons disabled in JSF are also disabled in the SPA.

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:

[coveralls]

coverage: 98.32% (+0.008%) from 98.312%
when pulling 622b8a3 on feauter/206-integration-dataset-locks
into 0d9e8f1 on develop.

[ekraffmiller]

looks good to me!

[GPortas]

Looks good!