Splitting limo2.31.py into multiple files

[aaron97neu]

Related to #10

Limo2.31.py contains almost 3000 lines of python code. In addition to being a security risk (The server gives access to all functions defined in this file to the user - including internal functions), this is unwieldy and bad practice. These python functions should be split into multiple files, at the very least public and private (internal) functions.

See XINU for an example of good organization of a large project

[NQureshi850]

il see if i can handle this issue, it's gonna take a while since this file is massive and organizing it into multiple files is going to take some time.

[aaron97neu]

We should also consider another file for stucts, classes, and other objects as well

[NQureshi850]

I feel like for now, we should seperate the functions and see if we can make objects and structs out of them. Its easier to see once they are separated and grouped

[aaron97neu]

Note - All functions that are provided to the user will be marked in the code with the comment
# User Function
This should allow us to find these function quickly when we eventually split the file

Currently in CommutersAsObjects branch but should be merged into dev by May 2019