Move initializers into packages

This is a start for exposing the container initialization of Ember-Data. Having stand-along container initialization will allow us to use Ember-Data with `moduleForModel` in ember-qunit, and finally use real adapters instead of being limited to fixture adapter.

This first pass is very naive, but I'd like some feedback on an API before I go any further. I propose:

``` JavaScript
var container = isolatedContainer(); // as from EAK or ember-qunit
DS._setupContainer(container);
```

This implies a few other changes:
* [x] Ember-Data uses a *single* initializer, which just calls `setupContainer(container, application);`. The existing four-initializer setup goes away.
* [x] `initializers.js` -> `ember_initializer.js`
* [x] `setup_container.js` is used by `ember_initializers.js`. `setup_container.js` imports then uses the four functions created below (in order, `initializeDataAdapter`, `initializeTransforms`, `initializeStoreInjections`, `initializeStore`) and the ActiveModelAdapter initializer.
* [x] AMA's own initializer goes away.
* [x] `setupContainer` is imported and added to the `DS` namespace in `main.js` as `DS._setupContainer`.

A build of Ember-Data with this patch: [ember-data.js](http://uni.madhatted.com.s3.amazonaws.com/ember-data-setup-container/ember-data.js) [ember-data.prod.js](http://uni.madhatted.com.s3.amazonaws.com/ember-data-setup-container/ember-data.prod.js) (omg why are you using this in prod).

/cc @rjackson @cavneb @abuiles