586 dataset terms tab

[ekraffmiller]

What this PR does / why we need it:

Adds the Dataset Page Terms Tab in read only mode

Which issue(s) this PR closes:

• Closes Dataset Page: Terms Tab (Read Only Version) #586

Special notes for your reviewer:

Suggestions on how to test this:

Step 1: Run the Development Environment

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

Step 2: Test the feature

1. Create a Dataset in the SPA and check the terms tab. It should match the JSF terms tab, showing a default license and no additional terms.
2. In JSF, Go to the terms tab and choose Edit Terms. Add some values to the term fields. Go back to the SPA and view the added terms.
3. In the JSF, add a file to the dataset and make it restricted. Go to Edit Terms, and add terms of access for the restricted file. Go to the SPA and view the restricted file permissions and terms of access.
4. In the JSF, go to the Dataset Terms section of the Terms tab, and change the license to Custom Dataset Terms. Then fill in additional input for the custom terms of use. Go to the SPA and view the custom terms.
5. In the SPA, publish the Dataset, and view the Custom Terms in the Publish Dataset Modal, which should match what is in the terms tab. Check the Custom Terms link in the Publish Dataset Modal, it should link to the Dataset Page in a new browser tab, with the Terms Tab active.
6. In the SPA, test the Custom Terms link in the Dataset Summary. It should update the Dataset url to include tab=terms, and make the Terms tab active on the page.
7. View the new stories in Storybook for the Dataset Page, Terms Tab and Publish Dataset Modal.

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.307% (+0.03%) from 97.282%
when pulling d14fd40 on feat/586-dataset-terms-tab
into dcdb033 on develop.