A large refactor brining the adapter up to date with Ember-Data

First of all **apologies for this giant change all at once**. If we can find meaningful ways to break it up I am definitely amenable to that.

But if you are a current user of the ember-parse-adapter, I could really use your eyes and feedback on this.

* Update Ember and Ember-Data
* Use a top level `EmberParseAdapter` namespace.
* Up the QUnit timeout to something reasonable
* Point bower at the vendor/ directory
* Add a geo transform
* Add a file transform
* Login and signup do not manage the session token or current user
* Login and signup accept ad-hoc data, allowing for social signup calls
* Add a parse-date transform
* Provide a sessionToken property on the adapter
* Update the README
* Drop the custom relation overrides to `DS.hasMany` etc
* Drop `DS.ParseModel`. Any model using this adapter is stored by its name.
* Found a bug upstream, would be good to get a fix in here https://github.com/jquery/qunit/pull/578

Some downsides or controversial items:

* I think I have broken non-pointer relationships.
* I have dropped most of the currentUser and session-maintenance stuff. I think that is better done outside the adapter itself. Instead, I've provided a `sessionToken` property that can be set by whatever manages the session.
* I am unsure if this is compatible with Ember-Data versions newer than master from a few days ago. Many edge cases in Ember-Data have been fixed in the past few weeks, including some that ensure enough internal consistency (such as `typeKey` formatting) that we can be confident about using them.

But tests are good, passing, and the code is better organized than before. Please discuss and comment liberally.

**This will certainly break existing usage**. 

Much of my work on this over the past week has been in partnership with the wonderful team at http://www.turnstilelive.com/. Shoutout to them for being fantastic folks.