Change to orcid for alshub requests

[dylanmcreynolds]

The first request to ALSHub is based on ORCID, then if there is an LBLID, every request after that is based on LBLID:

splash-userservice/alshub/service.py

Line 105 in 937da77

raise UserNotFound(f'user {id} not found in ALSHub or could not communicate')

However, users can be put on proposals before they are given LBLIds. Now that we have a sample tracker, we run into this.

We found out from Sujata that the subsequent calls can be made by ORCID. If we switch to that, we can maybe not fall into this trap.

FYI, these APIs also work with ORCiD If this is something which would also work for your case. For example, 
https://alsusweb.lbl.gov/ALSGetProposalsBy/?or=0000-0002-1539-0297
https://als-esaf.als.lbl.gov/EsafInformation/GetESAF/?or=0000-0002-1539-0297

[GBirkel]

Addressed in #7 .