Enable ORCID API scope change from public to member

[ewhanson]

Issue description

There are currently two different API options for use with ORCID in OJS, the public API and the member API. The public API can read from ORCID and be used to verify the ownership of an ORCID in the OJS context while the member API can write authored works and reviewer contributions back to a user's profile. These are done on two separate API endpoints with two different OAuth scopes, /authenticate for the public API and /activities/update for the member API.

These scopes are linked to the access tokens that are generated by ORCID and stored in the database in OJS for use when interacting with the ORCID APIs. When a journal gets access to the member API, it makes sense they would want t he ability to then be able to push authored works to ORCID for already authenticated authors. This is currently not possible for a few reasons:

1. The current design for ORCID interaction does not accommodate manually resubmitting/triggering deposits to ORCID. (This can be changed/updated as desired on the OJS side of things.)
2. An already authenticated author will have their ORCID account linked with a /authenticate only scope with an access token that is limited to that scope. Because of the way these token/scopes work, new tokens would need to be generated with the new scope in order to push content from OJS to ORCID.

Ideas for improvement

A first step would be some of the post-publication ability for authors/users to update their ORCID as noted in #10338. With some of those in place, one low-hanging-fruit change would be an additional workflow for existing authenticated ORCIDs to be able to expand the scope allowed through OJS.

Additional considerations

Some improvements to this within OJS are possible, but there are other hard limitations due to the nature of the OAuth workflow and how the scopes work.