replacing the nested record implementation
allow pushObject to use both hashes and record instances
adjusting the method to get to the nested file
handling setting null
remove store related tests
make normalize work properly with nested records
make replacing automatically trigger arrayContentDidChange
remove store related tests. Adding warning about normalize, which doesn't seem to behave as it should
removing store related tests
fixing errors with attributes and readOnlyAttributes. Formatting.
add notifyChildren to child array, adjust recordPropertyDidChange to properly reset everything when called without key
adding preliminary tests (commented out still) to also test for record order
remove debugger line mistakenly committed the previous time
#writeAttribute was still 1.4.5, updating to master, fixes test fail for updating primaryKey value
misread a few things when updating #writeAttribute, so now really made it work with master
added #parentRecord computed property for backwards compatibility (query), and removing commented out code
remove contained runloop in #createNestedRecord as it is no longer needed and creates problems with caching in a child array
Improves nested store handling of certain circumstances.

SC.NestedStore#lockOnRead, which defaults to YES, is much too aggressive, locking even on attempts to read non-loaded records. This causes problems if, for example, a nested-store record's not-yet-loaded toOne relationship is read (e.g. by being bound to a view), locking it and triggering a load in the parent store. When the load returns, the locked record triggers a full nested-store reset (failing meanwhile to notify the nested-store record instance that it has loaded), or errors out if anything, anywhere in the nested store has changed.

This commit avoids locking nested-store records when read in EMPTY or BUSY_LOADING states. It also modifies the behavior of SC.Store#_notifyRecordPropertyChange, which is where chained store errors are thrown, to switch solely based on the chained record's editable state, and to avoid costly and blunt full-store resets in any case. This allows the parent store to correctly update nested stores when untouched and unlocked records are updated.
Fixes API inconsistency with nested records'  which was accepting but failing to check for a non-array argument.