Dependencies should be specified via Pip

[Jack McPherson]

Is your feature request related to a problem? Please describe.
Whilst not a strict necessity for Python projects, it's fairly conventional to specify dependencies via Pip, the de facto standard package manager for Python. This is achieved via a requirements.txt manifest file conforming to the expected format.

Describe the solution you'd like
A requirements.txt file located in the project root containing the necessary dependencies extracted from the existing setup script:

AutoTrader/setup.py

Lines 52 to 78 in 9478b62

 install_requires=[ 
     "numpy >= 1.20.3", 
     "pandas >= 1.3.4", 
     "art >= 5.7", 
     "PyYAML", 
     "bokeh >= 2.3.1", 
     "scipy >= 1.7.1", 
     "finta >= 1.3", 
     "tqdm>=4.64.0", 
     "importlib-resources", 
     "Click", 
     "requests", 
 ], 
 extras_require={ 
     "dydx": ["dydx-v3-python"], 
     "ccxt": ["ccxt"], 
     "oanda": [ 
         "v20 >= 3.0.25.0", 
     ], 
     "ib": [ 
         "ib_insync >= 0.9.70", 
     ], 
     "yfinance": [ 
         "yfinance >= 0.1.67", 
     ], 
     "dev": ["black"], 
 }, 

Describe alternatives you've considered
We could separate out the different profiles (i.e. distinguish between production and development requirements) but this seems overengineering at the moment.

Additional context
None.