Create mature OIDC/OAuth support tooling

[chmc3]

Currently the UW Shibboleth idP has enabled the OIDC plugin to support OIDC connections.
However, the configuration of OIDC is done by an engineer only. This makes OIDC integrations costly and complex, compared to the current SAML integrations that are supported via the SPReg tool.
This issue is to track the efforts that would be put into determining our standard options for OIDC integrations (as we have in https://wiki.cac.washington.edu/display/infra/Shibboleth+Service+Provider+Support), and standardizing the claims that we would be releasing.
We would also develop SPReg into providing an option to automatically register an OIDC client, to select what claims you would like to release, and to view any OIDC registration as you can currently with SAML registrations.
This issue once prioritized will be split into multiple issues to break out the different parts of this work.

[chmc3]

First step, break down into smaller buckets so we can start going through the larger effort a bit at a time.