Feature/twitter oauth

[phillipjf]

This MR switches Twitter login over to use Twitter OAuth2.0 for fetching the username. This is primarily for historical purposes to continue using Twitter usernames for identifying users. Due to changes with the Twitter API, the friends functionality is no longer feasible to maintain and was not exposed in the UI anyways. Flask-Dance project even removed Twitter in a recent release Flask-Dance#416

BREAKING: This MR includes a migration to remove the friends association in the DB.

Resolves #21.

[phillipjf]

@joerick I think this covers everything to resolve #21. Will need to get the OAuth 2.0 Client ID and Client Secret from the Twitter Developer Portal and set the new environment variables (TWITTER_OAUTH_CLIENT_KEY, TWITTER_OAUTH_CLIENT_SECRET, OAUTH_REDIRECT_URI) accordingly.

[joerick]

If you have a chance to look at why CI is failing, that would be much appreciated! Something dependency-based.

By the way, another thought I had was... the site is hosted on Heroku, it uses their buildpacks, not the Docker config. Do you know if the switch to pyproject.toml will work other there?

[phillipjf]

If you have a chance to look at why CI is failing, that would be much appreciated! Something dependency-based.

Fixed this, the reference to the snapshottest package was the culprit. Also a couple tests needed updating.

By the way, another thought I had was... the site is hosted on Heroku, it uses their buildpacks, not the Docker config. Do you know if the switch to pyproject.toml will work other there?

I think this will work with the empty setup.py as recommended here: heroku/heroku-buildpack-python#834 (comment)

[joerick]

Brilliant! Lets give this a try...

[joerick]

It works!

[joerick]

Awesome. Thank you so much @phillipjf for this! Once I had all the API creds in the right place, it worked flawlessly.