115 - Dataset summary continued

[MellyGray]

What this PR does / why we need it:

Originally from a comment Philip left at #112 (comment)

After some discussion in the frontend meeting we decided to do the following changes in this PR:

1. Handle Persistent Identifier, Publication Date, Citation Date and Alternative Persistent Id to show them in the Citation Metadata accordion if they apply.

• I added the frontend logic, but the e2e won't display these fields until this change is implemented in js-dataverse. See #66, #65, #64

3. For Author No separation between name, affiliation, identifier type, and identifier. Affiliation should be in parentheses.

• I added the frontend logic, but the e2e is mocked until this issue is implemented in js-dataverse. See #63

4. ORCID there is no link

• No changes applied regarding the ORCID link in this PR. I'd prefer to see how this change is handled in the API/js-dataverse. If this is finally applied using displayFormat, then no change will be required in the frontend. I created a frontend issue to keep track of this in case some change is needed Display the authorIdentifier metadata field as a link #119

5. For Point of Contact
   For privacy reasons, the email should be hidden. Instead we mention a button (that doesn't exist yet in the SPA). See also https://guides.dataverse.org/en/5.13/installation/config.html#email-privacy

• Hidding the email needs to be applied in the backend so it never reaches the SPA. So it'll keep showing until changes are applied to the API
• Message 'Use email button above to contact.' added to this PR

Which issue(s) this PR closes:

• Closes [Spike - Frontend] Dataset summary, continued #120

Special notes for your reviewer:

Read carefully the description above. In summary, I only applied frontend changes but the backend work is pending.

Suggestions on how to test this:

1. Follow steps described at 95 - Invoke js dataverse use cases in the dataset page #112 to run the application using the development environment
2. As I explained above, the backend work is pending, so the only way to check the changes is by going to the Storybook and looking at the Dataset page with the mocked data.

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

The correct one is the left one:

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

Additional documentation:

[ekraffmiller]

Looks good - I can see the expected changes in the Data Summary section, approved the changes in Chromatic.

[kcondon]

@MellyGray I'm seeing an additional field in storybook, previous dataset. What is that?