isolatedContainer should know what not to instantiate

No reason to make people write this boilerplate themselves, right?
Add default config setup.

Allows specifying configuration in the following files:

* `config/environment.js` - This is loaded in all enviroments.
* `config/environments/production.js` - This is loaded when
  building with `grunt dist`.
* `config/environments/development.js` - This is loaded when
  building a normal development server (via `grunt server` generally).
* `config/environments/test.js` - This is loaded when running tests via
  either browsing to `/tests` URL or running via karma.
Don't destroy global config object

This will encourage people not to destory their window.ENV object by
reassigning it a completely new value.

The environemnt specific files should load after `environemnt.js` has
loaded. This way the values assigned to `window.ENV` in those
environment specific files can overwrite any defaults set in
`environment.js`

I have also cleaned up the comments somewhat and included a simple
example of setting a config value.
Bump ic-ajax

Bump to the version of ic-ajax that distinguishes
between ic.ajax and ic.ajax.raw
Changed APIMethod & proxyURL to use prettier configuration names under api hash
Changed to use new configuration options from package.json
Changed to use new configuration options
Cleaned up variable names
api.namespace is now being passed to routes.js
Changed to accept namespace argument
namespace argument is now used to setup the server namespace
Task options are used to configure proxies in Karma
Fixed wrong variable name after renaming
Removed string template from property name because grunt wasn’t replacing the value.
Added test for API Stub
Removed some empty lines
Moved proxy configuration into karma.js

Conflicts:
	karma.conf.js
Added expressServer to karma:test, karma:ci and karma:browsers tasks
Removed proxyMethod argument from server and test:server tasks
Add ic.ajax to .jshintrc
Fixed the test
Fixed test for ic.ajax 0.2
Add default config setup.

Allows specifying configuration in the following files:

* `config/environment.js` - This is loaded in all enviroments.
* `config/environments/production.js` - This is loaded when
  building with `grunt dist`.
* `config/environments/development.js` - This is loaded when
  building a normal development server (via `grunt server` generally).
* `config/environments/test.js` - This is loaded when running tests via
  either browsing to `/tests` URL or running via karma.

Conflicts:
	config/environments/development.js
	config/environments/production.js
	config/environments/test.js
	tasks/options/rev.js
Don't destroy global config object

This will encourage people not to destory their window.ENV object by
reassigning it a completely new value.

The environemnt specific files should load after `environemnt.js` has
loaded. This way the values assigned to `window.ENV` in those
environment specific files can overwrite any defaults set in
`environment.js`

I have also cleaned up the comments somewhat and included a simple
example of setting a config value.

Conflicts:
	config/environments/development.js