Dataset page: show deaccession reason and info

[ChengShi-1]

What this PR does / why we need it:

We are missing showing the deaccession reason in the Dataset page.

Which issue(s) this PR closes:

• Closes Dataset Page - Show deaccession reason and info #656

Special notes for your reviewer:

js-dataverse version should be updated in package.json
waiting for IQSS/dataverse-client-javascript#292

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.
Before running next step, be sure have a fresh unstable dataverse image.
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
2. publish it
3. In edit dataset button, click deaccession the dataset with a deaccession reason
4. check if the reason is shown
5. also, check the version tab, check if the version has the deaccession reason included

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.805% (-0.3%) from 98.07%
when pulling 6262512 on 656-dataset-page---show-deaccession-reason-and-info
into 4684edf on develop.

[g-saracca]

Just one question and styling suggestion.

[g-saracca]

@ChengShi-1 we have some merge conflicts

[ChengShi-1]

@g-saracca Hi German, thanks for your review. Conflicts merged, and js-dataverse updated to newest alpha version.

[ofahimIQSS]

not really sure why but I keep getting a blank screen when I navigate to http://localhost:8000/spa

[ChengShi-1]

not really sure why but I keep getting a blank screen when I navigate to http://localhost:8000/spa

@ofahimIQSS Hi Omer, I check this branch again and don't meet this situation. Could you please re-build the environment again see if it still happen?

• Execute npm i
• Navigate with cd dev-env. Before running next step, be sure have a fresh unstable dataverse image.
• Start the environment using./run-env.sh unstable.
  and verify the environment,

[ofahimIQSS]

looks good, merging.