Bug 1087811 - [email] update minification step to work with newer ES6-ish features

Introduces `build/esomin.js`, to handle a dir or file-based optimization of .js files. By default, it supports an AST-based minification via esprima/escodegen, but a different minification function can be used if desired, and a comment on how to use jsmin is in the docs for that file.

Email and calendar were updated to use this minification approach, which should allow them to use some ES6 features.

Before this change, email used uglify2, as provided by r.js, but uglify2 lags in support for these newer features. While the minification was greater with uglify2, it is only a 10% loss with this new approach, and it opens up email to consume shared components that may use newer features like template strings (like possibly the newer gaia custom elements).

For calendar, it got (and still gets) the jsmin treatment on script src files mentioned in its index.html, but it was not getting any other minification on the other files dynamically loaded by the AMD loader, or for the script loaded into the worker. Now, if GAIA_OPTIMIZE=1 is passed in the build (which happens for production/device builds), this extra minification happens.

Calender could opt for the jsmin path for all files. The downside is that jsmin removes line breaks, so it creates more of a challenge when trying to debug or when getting error stack traces. When I tried the "all jsmin" route, these were the application.zip file sizes, in bytes:

    723,425 master
    604,264 this branch, astMinify
    575,637 this branch, jsmin

If this new method cannot minify the file due to malformed JS or an unsupported AST structure, the file is just skipped. So the failure case is just that a file may end up larger than it would otherwise, but will still work, and the build will continue without interruption. A log message is emitted though, in case the developer wants to track down the minification problem.
requirejs.optimize does css concatenation/comment stripping, and does module concatenation for optimization reasons. So I think that API name still fits. I probably should have called the "optimize" build config property "minify" instead, since it only controls the minification. I can see doing that in an r.js 3.0 when the API can have breaking changes.