Separate loading and error handling for DOI, Organization, and Person pages

Purpose

Currently, all of the data is fetched in one big pass. These changes split up the query into two separate queries that can run in parallel, allowing it to quickly fetch and show the metadata for the DOI, organization, or person, while loading the related content.

Additionally, if an error occurs during the related content loading, the metadata section will still be shown, and an error message will only be shown in the related content section.

Approach

For each page, the query has been split up into two queries, metadata and related content, that run in parallel. They each have their own rendering and handling logic

Open Questions and Pre-Merge TODOs

Learning

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Reviewer, please remember our guidelines:

Be humble in the language and feedback you give, ask don't tell.
Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
Offer suggestions on how to improve code e.g. simplification or expanding clarity.
Ensure you give reasons for the changes you are proposing.

Merge 0c1e88a733cb76feb6bed3995c4fddb23bd724c1 into 1966678c53c19270849b1aa7227c...
Project: akita	Commit: `723fb7a9be ℹ️`
Status: Passed	Duration: 02:13 💡
Started: Jan 22, 2024 1:06 PM	Ended: Jan 22, 2024 1:08 PM

datacite / akita