Use addObject when updating record arrays

Currently using pushObject which means creating an object, adding it to the array, then saving the object results in the object being in the array twice.
Add test for RecordArray change to addObject.

Creating a new model, inserting into an existing RecordArray and calling save should not duplicate the model in the RecordArray.
Fixing loading the correct adapter in belongsTo and hasMany relations
Merge pull request #334 from josbeir/master

Fix issue #333 Relations don't have proper adapter set when using application store
Fix embedded hasMany not becoming dirty after save

Steps to reproduce:
1. Modify an item of an embedded hasMany array
2. Save the array (or the individual item)
3. Modify the item back to its original state

The item is clean when it should be dirty
Merge pull request #322 from dwickern/embedded-hasmany-dirty

Fix re-dirtying embedded hasMany after save
Register store:application as store:main if it exists. Fix tests to use App.destroy
Merge pull request #337 from ckung/master

Register application store if exists. Fix tests to use App.destroy.
Rename dataAdapter to data-adapter
Merge pull request #342 from teddyzeenny/data-adapter

Rename dataAdapter to data-adapter
Change path of jquery again
Fix container not being set on materializRecord in embeddedHasManyArray for deeper relationships
Merge pull request #344 from ckung/master

Fix container not being set on materializRecord in embeddedHasManyArray ...
Default relationship key to the property key
Merge pull request #346 from ckung/master

Default relationship key to the property key
Fix re-dirtying non-embedded hasMany after save

Save did not update the original content of the array to
reflect the new original state
Merge pull request #299 from Connorhd/patch-1

Use addObject when updating record arrays
Merge pull request #349 from dwickern/dirty-hasmany

Fix re-dirtying non-embedded hasMany after save