356 publish dataset

[ekraffmiller]

What this PR does / why we need it:

Which issue(s) this PR closes:

Closes #356

Special notes for your reviewer:
I wasn't able to add the major and minor version numbers to the popup, because they aren't currently part of the Dataset model. I added an issue for this: #428

Suggestions on how to test this:
Review the PublishDatasetModal Stories: http://localhost:6006/?path=/story/sections-dataset-page-publishdatasetmodal--default
Steps to test in the SPA:

1. Create a new dataset, which will be a Draft version.
2. Go to the Dataset Page, Click Publish Dataset Menu, and Publish dropdown
3. Click continue
4. The Publish Dataset should close and the "Publish in Progress" alert will appear on the Dataset Page.
5. When the publish is completed, the "Publish in Progress" will disappear and the Dataset will be version 1.0
6. Edit the Dataset Metadata and choose publish again.
7. Now the Publish Dataset Model will give an option of Major or Minor release.
8. Choose the version update type, and click continue.
9. The Dataset will be published again with the new version chosen (either + 1.0 for Major update, or + .1 for Minor update

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:

[GermanSaracca]

All the requested changes were implemented, approving 🚀

[GPortas]

@ekraffmiller Can you please resolve merge conflicts? Thanks!

[GPortas]

@ekraffmiller

New conflicts have emerged, please can you resolve them?

On the other hand, can you describe the steps to test this UI change? For example, specific storybooks, maybe a short description in Suggestions on how to test this would be very helpful. Thanks in advance!

[ekraffmiller]

I fixed the merge conflicts and updated the notes for testing 👍

[GPortas]

@ekraffmiller

I am encountering the following error in the files tab when publishing the created dataset for the first time.

I attach also a recording:

Untitled.mov

Could this be related to the change from draft to latest-published as default?

[ekraffmiller]

@GPortas I encountered that error before, the fix for it may have been lost in the merge, I will look into that.

[GPortas]

Thanks for addressing the changes! I haven't encountered that error again.

The major version update seems to work correctly. But the minor version update does not update the minor version, instead it updates the major version. For example, if I am on version 1.0 and select minor, it publishes 2.0 instead of 1.1. I have checked that in JSF it publishes 1.1.

I attach a recording:

minorerr.mov

[ekraffmiller]

@GPortas thanks for catching that! I made the fix and updated the e2e tests to check that.

[GPortas]

@ekraffmiller Thank you for addressing the changes!

Merging.