Delete File - SPA Integration

[g-saracca]

What this PR does / why we need it:

Implements the Delete File option on the Edit File dropdown in the File Page.

Which issue(s) this PR closes:

• Closes File Page: Delete File #590

Special notes for your reviewer:

Suggestions on how to test this:

Step 1: Run the Development Environment

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

Step 2: Test the feature

1. Create a dataset and a file in it.
2. Go to that file and click on Edit File > Delete. Only one message should appear in the dialog "The file will be deleted after you click on the Delete button.".
3. Click the Delete button in the dialog, after deletion a success toast should appear and you should be redirected to the parent dataset.
4. Add a new file to that dataset and then publish the dataset.
5. Go to that file and click on Edit File > Delete. Two messages should appear in the dialog now.

• "The file will be deleted after you click on the Delete button."
• "Files will not be removed from previously published versions of the dataset."

6. Click the Delete button in the dialog, after deletion a success toast should appear and you should be redirected to the parent dataset.

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

Yes.

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

Additional documentation:

[coveralls]

coverage: 97.367% (+0.03%) from 97.342%
when pulling 496d269 on feat/590-delete-file
into 5a2e625 on develop.

[g-saracca]

Solved conflicts and using latest alpha version of js-dataverse

[ekraffmiller]

Looks good! A couple of comments

[g-saracca]

@ekraffmiller all changes applied. Let me know what you think about the key prop.
Thanks for the review!

[ekraffmiller]

looks good, approved!

[ofahimIQSS]

hello! I see some branch conflicts on this PR. Can you please resolve before I can merge. Thanks!

[g-saracca]

@ekraffmiller could you reapprove? I just merge develop into the branch to solve conflicts 👍🏼

[ekraffmiller]

looks good, approved

[g-saracca]

All done @ofahimIQSS 👌🏼

[ofahimIQSS]

PR looking good - merging.