Update ORCID field to support inputs in both short and long (URI) form

[joemull]

Is your feature request related to a problem? Please describe.
Currently some inputs to the ORCID field cause problems with DOI registration, or don't behave as expected in other ways.

Describe the solution you'd like
Use regular expressions to detect various ORCID forms and store a uniform version of the ORCID, even if it is still served or displayed in various ways through the GUI.

[alainna]

Please reconsider this. There should be no manual inputs of ORCID iDs. Rather, perhaps there should be a standardisation of input for ORCID iDs -- and, tbh, DOIs. e.g. if iD isn't in X format (0000-000x-xxxx-xxxx / https://orcid.org/0000-000x-xxxx-xxxx), then it should be updated accordingly. If the input is unable to be standardised, then user is shown error and told how to correct ("ORCID iD must be in X format").

[ajrbyers]

Please reconsider this. There should be no manual inputs of ORCID iDs.

Its a great goal but realistically, thats not going to be possible.

[ajrbyers]

if iD isn't in X format (0000-000x-xxxx-xxxx / https://orcid.org/0000-000x-xxxx-xxxx), then it should be updated accordingly. If the input is unable to be standardised, then user is shown error and told how to correct ("ORCID iD must be in X format").

This is the goal here. We will store it in a single format after checking that its valid.