Feature: legacysupport

### Here I have included:

 * the legacy haxelib code base, with the updates needed to live in a `legacy/` subfolder.  I've submitted a patch to the compiler team for these as well.
 * a new `site.sh` to build the site structure with the new site and the legacy site living side by side.
 * the `.htaccess` files for this to play nice with apache, including redirecting remoting calls to "/" through to "legacy/index.n", while other requests to "/" go to "index.n".

I will need somebody to update "site.bat" to match "site.sh", I'm not familiar enough with windows bat files to do this myself without rebooting into windows :)

This is all working on my apache2 setup.  Need mod_rewrite enabled, and I've got mod_deflate enabled too, but if that's not on the current server we can just delete those lines.

### The next steps

 * Separate out the Haxelib2 Site from the Haxelib 2 remoting API.
 * The site will go to /index.n
 * The remoting API will go in /api/2.0/index.n
 * Future changes to the remoting API that break backward compatibility can use a different version number for the API end point.