Server: Support database checking checkAuth()

[TiE23]

Switching to using JWT instead of GraphQL hits to the database sped things up a lot, but it essentially means that if I ban an account they will have open access for as long as their JWT is valid and they do not log back in. I need to restore the option to have checkAuth check the database for the user's current status.

Restoring that step will not be difficult (just look at the diffs for ISSUE #78's branch), but deciding how to smartly re-check will be important.

Should I have pings to the server happen at random? For certain raised-sensitivity queries/mutations? For all mutations? Or should I look into tracking JWTs that were issued and have every checkAuth() hit that table and look for expired (in this case, forcibly) with every hit to the server and pray it's fast?

[TiE23]

Some thoughts later on:
I think all mutations should have a deep check.
I would like to maintain the checkAuth() function. So if possible make the deep check an optional argument.