Resolve RuntimeWarning about interacting with database during AppConfig.ready()

[angela-tran]

Should we be worried about this / look into it further? What can go wrong if "the app registry has not been fully populated" / what does that even mean?

Looking into this a little further, I found some Django docs that correspond with the RuntimeWarning we're seeing. This section warns against interacting with the database in AppConfig.ready():

Our OAuthAppConfig interacts with the database by querying for all AuthProviders.

The "Application intialization process" documentation describes how the app registry gets populated and why "premature database queries are discouraged": https://docs.djangoproject.com/en/5.0/ref/applications/#initialization-process

But I'm not sure if there's a better place for us to register our Authlib configurations.

Maybe we should register each AuthProvider's configuration upon the first attempt to actually use it?

Originally posted by @angela-tran in #1809 (comment)

[thekaveman]

Related: #1379

[angela-tran]

Exceptions from misconfiguration of AuthProviders could also be swallowed by the way the code works right now, and the fix to this ticket would also fix that