Actually make use of the "users" database table.

Also change some of the route names to be login-provider specific as
the eventual plan is to implement more than just twitter.