Monkey-patch ssl in __init__ to fix grequests warning/error

[tianyizheng02]

The grequests package monkey-patches ssl upon import, but this must be done before all other imports. This PR imports gevent at the very top of __init__.py and explicitly monkey-patches everything.

Currently, without this patch, importing the news module will raise a MonkeyPatchWarning:

>>> from pittapi import news
.../lib/python3.12/site-packages/grequests.py:22: MonkeyPatchWarning: Monkey-patching ssl after ssl has already been imported may lead to errors, including RecursionError on Python 3.6. It may also silently lead to incorrect behaviour on Python 3.7. Please monkey-patch earlier. See https://github.com/gevent/gevent/issues/1016. Modules that had direct imports (NOT patched): [...]. 
  curious_george.patch_all(thread=False, select=False)

while importing textbook will raise this warning as well as a RecursionError:

>>> from pittapi import textbook
.../lib/python3.12/site-packages/grequests.py:22: MonkeyPatchWarning: Monkey-patching ssl after ssl has already been imported may lead to errors, including RecursionError on Python 3.6. It may also silently lead to incorrect behaviour on Python 3.7. Please monkey-patch earlier. See https://github.com/gevent/gevent/issues/1016. Modules that had direct imports (NOT patched): [...]. 
  curious_george.patch_all(thread=False, select=False)
Traceback (most recent call last):
...
RecursionError: maximum recursion depth exceeded

With this patch, both modules can be imported with no warnings or errors.

References:

• Grequests is creating Recursion errors due to invalid monkey patch spyoungtech/grequests#150
• SSLContext infinite recursion in Python 3.6 gevent/gevent#1016

[tianyizheng02]

flake8 raises errors about imports not being at the top of the file:

./pittapi/__init__.py:27:1: E402 module level import not at top of file
./pittapi/__init__.py:28:1: E402 module level import not at top of file
2     E402 module level import not at top of file
2

This is true, but it's also entirely intentional, since we need to monkey-patch before all other imports, including other imports in __init__.py.

[tianyizheng02]

Also, for some reason these monkey-patching warnings/errors only appear when you import modules normally, and they don't occur when modules are imported during tests. Not sure why this is, but we could've caught this issue much sooner had these warnings/errors appeared during tests.