embedded associations are now automatically added to the parent's transaction
This PR represents a lot of refactor work on the rest_adapter_test unit tests.

All of the tests which are passing have been modified to match their original passing conditions. There is one failing test included (which I believe is legitimate), that uncovers an issue with sideloading data.

Summary of changes:
- added flagEquals / stateEquals assertion helpers
- added comments for test helpers
- removed teardown for tests (all tests remained green after doing so)
- cleaned up scoping for tests -- globals only used for configuration, locals used for test data
- relocated helper functions to top of test
- removed unnecessary var definitions
- created a consistent test format:
- test setup code is grouped together
- test assertion code is grouped together
- whitespace between setup and assertion code
- comments above each individual assertion and setup block
- each test should have a state and flag assertion after a model change state

The new flagEquals() assertions and stateEquals() assertions should probably be audited to ensure that the state of the records should actually be what the assertion says they are. While re-writing these tests, I personally disagree with some of the flags set for the given record states.
Fix rest adapter failing tests
Merge pull request #1 from teddyzeenny/reset-adapter-tests

Fix rest adapter failing tests
remove transaction-level relationship book-keeping
assume EXTEND_PROTOYPES === false
Merge pull request #950 from emberjs/pr/942

Pr/942
Renamed flagEquals to enabledFlags & flagsEqual to enabledFlagsForArray
Merge pull request #951 from Mochaleaf/master

Renamed flagEquals to enabledFlags & flagsEqual to enabledFlagsForArray
bump ember
Reject the error
Merge pull request #952 from stefanpenner/rsvp_reject

Rsvp reject
Merge pull request #948 from ghempton/transaction-relationships

Clean up transaction relationship book-keeping
Merge pull request #711 from ghempton/embedded-transaction

embedded associations are now automatically added to the parent's transa...
Persist errors object on models.

This is closer to what people expect, and allows users to add observers
on the
errors object itself rather than on the model.

The errors object is cleared when the model becomes in flight, which
supports
"base" errors not associated with a property (and therefore not cleared
on
property set).

[Fixes #852].