Sub-epic: Update python libraries

[jason-upchurch]

Summary

From issue fecgov/openFEC#3782 and fecgov/openFEC#3940 the following packages do not seem to have breaking changes. "Unused" packages are still identified below to afford another opportunity to double check they are not used.

package	location	current	newest	GitHub issue to upgrade
cfenv	requirements.txt	0.5.2	0.5.3
psycopg2-binary	requirements.txt	2.7.4	2.8.3
Flask	requirements.txt	1.0.2	1.1.1	fecgov/openFEC#4026
Flask-Cors	requirements.txt	3.0.6	3.0.8
Flask-RESTful	requirementst.txt	0.3.6	0.3.7
python-dateutil	requirements.txt	2.4.2	2.8.0
sqlalchemy-postgres-copy	requirements.txt	0.3.0	0.5.0
networkx	requirements.txt	1.11	2.3
SQLAlchemy	requirements.txt	1.3.1	1.3.7
icalendar	requirements.txt	3.9.1	4.0.3
GitPython	requirements.txt	1.0.1	2.1.12
gunicorn	requirements.txt	19.7.1	19.9.0	fecgov/openFEC#3961
webargs	requirements.txt	5.3.1	5.4.0
ujson	requirements.txt	1.33	1.35
requests	requirements.txt	2.21.0	2.22.0
elasticsearch	requirements.txt	5.5.1	6.3.0	fecgov/openFEC#4065
elasticsearch-dsl	requirements.txt	5.4.0	7.0.0
marshmallow-sqlalchemy	requirements.txt	0.15.0	0.17.0
smart_open	requirements.txt	1.7.1	1.8.3
redis	requirements.txt	3.2.0	3.3.8
pytest	requirements-dev.txt	3.7.4	5.1.1
pytest-cov	requirements-dev.txt	2.5.1	2.7.1
factory_boy	requirements-dev.txt	2.8.1	2.12.0
nplusone	requirements-dev.txt	0.8.0	1.0.0
webtest	requirements-dev.txt	2.0.27	2.0.34
click	requirementst-dev.txt	6.7	7.1
codecov	requirements-ci.txt	2.0.9	2.0.15

[patphongs]

@jason-upchurch Can you please clean up this ticket? It seems large especially because there's so many packages we want to update

[jason-upchurch]

@patphongs I've cleaned the table to remove incorrect entries. I think as we get this assigned, we could let the developer decide which packages should be split off into other issues based on their findings?

[PaulClark2]

Seems to me, we could use this ticket as a sort of checklist. We'd create a new ticket for each package that we decide to upgrade.

[jason-upchurch]

Seems to me, we could use this ticket as a sort of checklist. We'd create a new ticket for each package that we decide to upgrade.

@PaulClark2 @patphongs I like this idea a lot. I'm updating the table to include an issue column so that we can link to the issue that resolves the package.

[lbeaufort]

FYI, we need to stay on elasticsearch and elasticsearch-dsl version 5.x.y because that's the version of elasticsearch we're running in cloud.gov. https://cloud.gov/docs/services/elasticsearch56/

[PaulClark2]

closing in favor of #165