Bug 1046815: Update mozharness configs

This almost re-syncs our mozharness config files with the "real" ones in mozharness. The remaining differences are a few references to /tools; I am trying to sort out those differences with Release Engineering, but that may take some time.
The declarative interface will take an artifact name and **the path of the artifact inside the docker container**. And then use something like `docker cp` to copy the file out of the container and upload it. if the file is missing an error artifact will be uploaded, so that when inspecting tasks it's easy to see which artifacts was uploaded and which wasn't found in the declared location on the docker container.

Anyways, what we should do is document where artifacts to be uploaded are stored within the docker container when it shutsdown. Again, ideally we have some YAML format for writing tasks to be parameterized and stored on disk for later submission. @lightsofapollo might have some plans on how to do this, I don't know.

Otherwise, a section in the README file on how to run these tests is also fine :)