Move new_project.zip into seperate repository about tools

[lschmierer]

This seems good.

[ebkalderon]

Copied from Gitter at April 2, 2016 7:42 AM for records:

I think that's a good idea overall to have the new project standard be in a non-binary file, but I disagree on a few points.

1. I don't think that should store an actual Cargo.toml inside the template project. I thought that was decided a while ago after some Gitter discussion that we should generate a real Cargo project by calling into actual Cargo and then applying changes on top of that.
2. I don't believe we should have to connect to the Internet to generate a new project. That seems a little overkill IMO. Once amethyst_tools is installed, it should work on your machine as-is without having to download further data that could be more efficiently stored locally.

[lschmierer]

amethyst new should not connect to the internet, therefore I suggest using the template as submodule within the tools repo.

[ebkalderon]

What should we call this repository? Perhaps amethyst/project_template or similar?

[ebkalderon]

I think this can be closed with #32 being merged.