Support other kinds of authentication besides Auth0

[MoralCode]

it seems as though this ClassClock API may be useful on its own, independent of the client app as a way for applications to have their own generic (non-individualized) way to store school bell schedule data that provides a bonus in terms of interoperability with other apps that are based on a ClassClock-formatted API

Since Auth0 is already fairly standards-based, it shouldn't be too crazy to try and abstract it and allow for other auth providers, such as google (see this tutorial).

This would likely require:

• documenting the required roles and permissions the API needs
• decoupling the role and permission strings into some kind of constants file
• creating a function in each auth class to identify the role of a user since each provider may do it differently
• TBD