Transition trapp to be a valid Python package

[KartavyaSharma]

trapp has a willy-nilly project structure right now, I just built it with a "whatever feels right to me" approach. As a result, no conventions are being followed for how it should be structured. There are two possible ways this could go, depending on one's perspective on if trapp is a primarily Python or Bash-based project. The entry point for all Python scripts in trapp stem from the start.sh script, which has a significant amount of BASH code to test for dependency presence, along with setting up the backup daemon and running a Python script that backs up to S3. It is possible to argue that trapp is a shell package-like program.

However, there is a LOT of Python code in the project, especially within the auto module. If the decision is made to consider this a Python package by the sheer amount of Python code floating around, this link could be of help w.r.t project structure/following conventions:

https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/