Refactor repository to just be Java Resident Passenger Source Code

[DavidOry]

Unlike TM1, TM2 requires multiple repositories, which will allow:

1. tm2py to be a proper Python package, with documentation focused on the APIs and functionality of that code.
2. travel-model-two to be a focused repository containing only the Java code for implementing the resident passenger component. This repository would be deprecated in TM2.3's move to ActivitySim.
3. travel-model-two-configs will contain the configuration files needed to implement scenarios. Once the model is up and running, this will be the primary place where MTC makes changes.

The question is then where to put all the other stuff that has been accumulating in the travel-model-two directory, which includes the following:

1. Documentation, some of which is relevant, some of which is not.
2. Spatial files, including MAZ and TAZs.
3. Utilities for doing specific analyzes, some of which will remain relevant in TM2.2+
4. Visualizer files, which have largely been replaced by Tableau, but could be useful for TM2.1- users
5. Calibration and validation files

Should these all go in travel-model-two-configs? Or somewhere else?

@lmz, @gregerhardt: thoughts? Related to BayAreaMetro/tm2py#148.

[DavidOry]

Per June 12 meeting, moving this branch to develop as our first pass at organizing the repositories.

[DavidOry]

@vivverma9 For your telecommuting work, please re-base to the updated develop branch and start a pull request once you have made some commits. FYI @AshishKuls.