130 - Dataset citation thumbnail

[MellyGray]

What this PR does / why we need it:

This PR adds the dataset thumbnail logic to the UI. This is not yet connected to the API

Which issue(s) this PR closes:

• Closes [Spike - Frontend] Implement Dataset citation thumbnail #130

Special notes for your reviewer:

This is not yet connected to the API, it will need an API extension to get the dataset thumbnail.

Suggestions on how to test this:

1. Install the necessary dependencies using npm install.
2. Build the design system with cd packages/design-system && npm run build.
3. Navigate back to the root directory with cd ../../.
4. Start Storybook with npm run storybook.
5. Visit the Dataset Citation section in the Storybook a new story has been added to show how the thumbnail image will be displayed in the Citation block.

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

Yes, this PR introduces a user interface change.

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

Dataset thumbnail added to the Dataset View Mode

[coveralls]

coverage: 98.298% (-0.3%) from 98.58% when pulling 462ac44 on feature/130-dataset-citation-thumbnail into 97695ea on develop.

[GPortas]

Shouldn't a thumbnail image be displayed instead of the default image? @MellyGray

I'm on http://localhost:6006/?path=/story/sections-dataset-page-datasetcitation--with-thumbnail

[MellyGray]

@GPortas sorry, that was a last minute change and I mixed things 🙏 fixed now! I also fixed some merge conflicts

[GPortas]

@MellyGray Can you please resolve the conflicts? Thanks!

[GPortas]

It seems that we have another issue when building the app for beta testing: https://github.com/IQSS/dataverse-frontend/actions/runs/6732893099/job/18300451474

Can you fix it so we can stabilize develop as you did on the other PR?

Do you know how we can detect this before merging PRs? @MellyGray

[MellyGray]

@GPortas I fixed the merge conflicts

Also, both the storybook error and this one was caused by type errors so I added a new step to the Github action and to the precommit to check this type of errors