Decrease the size of the default container

[soulgalore]

The size of the container hasn't got any love for a while and the size has grown over time. Lets see how we can make it smaller + maybe build a couple of special containers as small as possible.

[soulgalore]

This actually a bigger thing than I thought. The problem is "hidden" feature of using npm-shrinkwrap. Most of our projects use that. That works fine so we know exact which version to use. Then running npm install --production also works fine for one project, only dependencies is installed (even though the dev dependencies exist in the lock file).

Running on Travis we use that lock file to install, so that lock file needs to also include the dev dependencies (you can create lock files without it by pruning and --production but that kind breaks CI.

For a project that then depends on a project with a npm-shrinkwrap file, and you run npm install --production it actually installs all dependencies including dev-dependencies :O

That means through the chain of the gecko driver download, that is used by browsertime, browsertime is used by the coach, and the coach is used buy sitespeed.io. If all these packages use a shrink-wrap file, all their dev dependencies ends up in npm run install --production for sitespeed.io. I need to file an upstream issue for this so at least I can understand how it should be used. But for now I've been removing shrink-wrap files. Potentially it can make install breaks for people but I don't see a way forward to fix this for now. When I'm finished I'll write down how much data we are actually are talking about.

[soulgalore]

Done.