Overview of the Feature Request

With an Open ID Connect Provider becoming an integral part of future Dataverse installations, it should be possible to deploy its configuration not just via API but also from a mixture of MPCONFIG sources.

An example how this looks like in other applications might be found in the Quarkus OIDC support: https://quarkus.io/guides/security-openid-connect#configuring-the-application

We should provide something similar, also to enable the new planned security filter to have access to this configuration without needing access to a database.

What kind of user is the feature intended for?
Sysadmin, Developers

What inspired the request?
The recent authn/authz efforts around the SPA.

What existing behavior do you want changed?
Currently you need to deploy an OIDC auth provider with a JSON file sent to an API endpoint, see https://guides.dataverse.org/en/latest/installation/oidc.html

This is cumbersome for testing with containers and containerized production environments.

Any brand new behavior do you want to add to Dataverse?
Nope. This is simply adding an additional config way for an auth provider.

Any related open or closed issues to this feature request?
#9227 / #9234 & #9229 / #9230