fix: only call ORCID well known endpoint on settings page

[ewan-escience]

Fix ORCID requests

Changes proposed in this pull request:

• Only call ORCID well known endpoint on section page
• Replace string 'MISSING' with null if coupling URL is missing
• Wrap code in try-catch statement to always be able to show the settings page

How to test:

• docker compose down --volumes && docker compose build --parallel && docker compose up --scale data-generation=0
• Log in with a non-ORCID account
• Navigate various user pages, like http://localhost/user/projects and http://localhost/user/settings. There should only be a noticable delay on the settings page

Note: It would be better to only fetch the data when needed when clicking the button, or asynchronously in the background. It might also be good to use caching. However, this PR only implements the minimum necessary, as this code is also being worked on in #1100.

Closes #1103

PR Checklist:

• [ ] Increase version numbers in docker-compose.yml
• [x] Link to a GitHub issue
• [ ] Update documentation
• [ ] Tests

[sonarcloud[bot]]

Quality Gate failed for 'rsd-frontend'

Failed conditions

27.8% Duplication on New Code (required ≤ 3%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[dmijatovic]

Just for the protocol: using this implementation, the LinkOrcid button only is shown if ORCID_REDIRECT_COUPLE is defined.

That is correct. We can apply additional logic in the apiLinkOrcidProps methods if needed.

[ewan-escience]

It is good to write down here that this PR now also contains caching.