New JSON Modlist format

There are two added parameters to FML: --mods and --modListFile. Both allow for resolution of mod resources (jars and zips) outside of the mods directory. Neither has any impact beyond allowing for the setup of a common repository for mods beyond the mods dir itself. It's goal it to assist mod pack makers, by allowing them to only have one central place for mods, and just injecting the mods list into minecraft through this means.

--mods is a simple, comma separated list of files (relative to the minecraft directory), that will attempt to load and be treated as mods.

--modListFile will point to a json formatted file. It tells FML two things, the first is a "repositoryRoot". The second is a list of maven specified mod locators, stored in maven directory format under said repository root. Note, additional parameters MAY be added to this to facilitate client/common/server setups. Consider this one the common one.

The JSON file (obviously, an example):

{
  "repositoryRoot": "/a/path/to/a/directory",
  "modRef": [
    "cpw.mods.ironchest:ironchest:1.7.2-6.1.10:universal",
    "appeng:appliedenergistics2:rv1-stable-1"
  ]
}

This will attempt to load files "cpw/mods/ironchest/ironchest/1.7.10-6.1.10/ironchest-6.1.10-universal.jar" and "appeng/appliedenergistics2/rv1-stable-1/appliedenergistics2-rv1-stable-1.jar" from under the repository root directory.

In theory this mechanism should allow for a "pool" of mods in a single location on disk, loaded by potentially many versions of mod packs, without having to duplicate into a mods folder.