🧹 Chore: Move Legacy travel-model-two Documentation

[DavidOry]

The current travel-model-two repository contains everything necessary to run TM2.1 and earlier, including the Java source code, application scripts, and configuration files. For TM2.2 and beyond, the model controller infrastructure lives in tm2py, scenario-specific configuration files will live in travel-model-two-configs, and the Java resident passenger component software will live in travel-model-two (though we may want to rename to travel-model-two-resident-passenger to make it clear what it is.

Right now, the legacy travel-model-two repository contains a host of useful, but not up to date information. Some of this information, e.g., process, is out of date and replaced by tm2py. Others, e.g., geographies, remains useful and should continue to live somewhere.

Progress:

• Sufficiently defined
• Approach decided
• Implemented

Considerations

The question is where should this documentation be moved to. @lmz, @gregerhardt: any thoughts? My initial thought is to move it to tm2py, so that web presence becomes a one-stop shop.

A similar question for where you want to put things like the MAZ and TAZ shape files. To me these should be in the configs directory. Thoughts?