295 - Display real dataset version information in the File Page

[MellyGray]

What this PR does / why we need it:

This PR adds the integration with js-dataverse to get the dataset version information from the getFile use case to display the data in the SPA File Page

Which issue(s) this PR closes:

• Closes Display real dataset version information in the File Page #295

Special notes for your reviewer:

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 breadcrumbs

1. Go to http://localhost:8000
2. Login as admin using username: dataverseAdmin and password: admin1
3. Create a new Dataset
4. Upload a file to the dataset
5. Go to http://localhost:8000/spa and select your dataset in the list
6. From the list of files in the Dataset page select your file to go to the File page
7. In the File Page check that the dataset version information such as the version labels and dataset citation matches the real dataset version information

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

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

Additional documentation:

[coveralls]

coverage: 97.179% (+0.002%) from 97.177%
when pulling 13b10e4 on feature/295-display-real-dataset-version-information-in-the-file-page
into c0beef9 on develop.

[GPortas]

Looks good overall!

Here I share a couple of UI details that should be fixed to match the JSF version:

Here is the JSF version:

[MellyGray]

Looks good overall!

Here I share a couple of UI details that should be fixed to match the JSF version:

@GPortas, I have updated the download URL, thank you.

However, regarding the date, I believe we all agreed some time ago to use the local standard for dates in the UI instead of the international ISO format. Therefore, in your case, you're seeing the Spanish standard date format, which will differ for US users. However, even for US users, it will not match the JSF format, because we are now using the local format instead of the international ISO format. The same thing is happening in any SPA date

[GPortas]

@MellyGray Can you please resolve the conflicts?

[GPortas]

LGTM