Fix environments

`-e <env>` and `--env <env>` are broken on the CLI interface right now. Simple naming mistake, I assume when the CLI was refactored. This didn't raise any issues with the test suite because we only test through the JS API. I began adding tests to `test/cli.coffee`, and was going to use the same assertions as the environments test in `test/compile.coffee`, but I quickly realized that the CLI interface is mocked and doesn't actually compile the project, so I can't assert whether the files exist in the public folder. I can add a test for this, just didn't want to start changing around the test suite without consulting with you first.

Also, is there a reason the accord bump and rc.9 commits are only on the v3#analytics branch instead of v3? That's why I have `package.json` as part of my diff.