Special cases to populate the "credential-to-be" in the Issuer app

[swcurran]

Currently, we use the data from the OIDC token to populate claims in the credential we will issue to the issuer via the ID Kit Issuer app. There are two special cases that we need to deal with:

• When the OIDC token is for the user "wa-admin" or "wa-user", instead of using data from the OIDC token, grab and map the data we have from the Admin app for the user into the credential-to-be claims.
• Likewise, when there is no OIDC token (because we are just using the time-limited GUID to control access), grab and map the data we have from the Admin app for the user into the credential-to-be claims.

Nice to have: In this scenario, when the data for the credential comes from the Admin data, it would be nice to have an config flag (env variable) that indicates if the pre-populated data can be edited or not. I'm not certain of there is a need for this, so minimal effort on this part.

[esune]

This has been addresses in #132, however it currently is only possible to test locally (when signing in as one of the pre-baked users) as the app doesn't yet have a switch to turn the authentication mechanism on or off.

The configurable authentication is being worked on as part of #109