Exclude chrome.js from the default externs - move to an environment

The chrome.js externs are becoming problematic because:

a) they are not standard browser externs
b) they cause naming collisions (see #1180, #1189)

The chrome externs should be moved to a custom environment. However, since a chrome extern set also needs the browser externs, a little bit of work would be required to do this.