Unable to update OAuth scope for authenticated ORCIDs

[ewhanson]

Describe the issue

As background, there are two different API types for ORCID, the public and member APIs. They each make use of different OAuth scopes when authenticating users. If OJS users authenticate their ORCID via OAuth with the ORCID service, they are giving permission to a specific scope depending on which API version the journal is using. If a journal switches to use the member API in order to deposit items (submissions/reviews) with ORCID, previously authenticated ORCIDs stored in OJS will not have the correct permissions to make the deposit because they were previously authorized with a more limited scope.

Describe the solution

OJS needs to be able to handle the switchover from the public API to the member API gracefully.

The following will accomplish this:

1. When a deposit is attempted with the member API, first check if the given user/author has the correctly scoped access token.
2. If not, send a new email template to the user/author explaining the situation and prompting them to re-authenticate their ORCID in order to push the item to ORCID.
3. Add functionality to the authorization email to handle depositing a specified record as part of the process.

TODOs, PRs, Notes

N/A