DRY up setup.py and get dependencies in place to start testing

[perobertson]

This cleans up the setup.py file so that it uses the requirements.txt to specify the dependencies. That way we dont get any conflicting requirements. I also set up the requirements.test.txt file which we can start adding to when tests get added to the project.

There are 2 ways you can try this out:

• python setup.py test (or python3 depending on your OS)
• pip install -r requirements.txt -r requirements.test.txt and then pytest

Example:

⇒  python setup.py test
running pytest
running egg_info
creating ttc_api_scraper.egg-info
writing ttc_api_scraper.egg-info/PKG-INFO
writing dependency_links to ttc_api_scraper.egg-info/dependency_links.txt
writing entry points to ttc_api_scraper.egg-info/entry_points.txt
writing requirements to ttc_api_scraper.egg-info/requires.txt
writing top-level names to ttc_api_scraper.egg-info/top_level.txt
writing manifest file 'ttc_api_scraper.egg-info/SOURCES.txt'
reading manifest file 'ttc_api_scraper.egg-info/SOURCES.txt'
writing manifest file 'ttc_api_scraper.egg-info/SOURCES.txt'
running build_ext
============================================================================= test session starts ==============================================================================
platform linux -- Python 3.6.6, pytest-3.8.2, py-1.6.0, pluggy-0.7.1 -- /home/perobertson/.pyenv/versions/3.6.6/bin/python
cachedir: .pytest_cache
rootdir: /home/perobertson/workspace/ttc_subway_times, inifile: pytest.ini
collected 0 items                                                                                                                                                              

========================================================================= no tests ran in 0.00 seconds =========================================================================