Almost complete population of OIDC from start to finish This will just about reconcile any resource in any namespace, create a unique name, generate cryptographic secret credentials, populate a secret for the application to use which contains these credentials, creates a two model application-provider blueprint, and will very soon finally expose the ingress for well-known for the domains given in the initial CRD. The only bugs I can clearly see are modifications cause some reconcilliation issues with the blueprint only as it crossess over with the existing reconciler and has some interesting but difficult to mitigate behaviour.