Add `replace` statement to composer.json

Add replace statement as described here https://github.com/magento-hackathon/magento-composer-installer#change-the-vendorname-of-your-module
Fixed missing comma
#179: Enabling group annotation on data provider
FIXES Exception : Strict Notice: Declaration of EcomDev_PHPUnit_Constraint_Layout_Block_Property::getActualValue() should be compatible with EcomDev_PHPUnit_Constraint_Layout_Abstract::getActualValue($other = NULL)  in lib/EcomDev/PHPUnit/Constraint/Layout/Block/Property.php on line 80
test case for array_merged config values -> creates array -> Exception "Warning: It is not yet possible to assign complex types to properties"
use array_replace_recursive instead
test case for config values from multiple files - expected behaviour would be that the most specific one prevails
switch order so that method annotations end up being loaded after class annotations
load fixture for class
fixes #204 getModelInstance() object to string
fixes #204 cast 2nd $modelClass to (string)
Merge pull request #191 from Schrank/fix_strict_notice

Fix strict notice
Merge pull request #196 from fooman/fixture-array-merge

Fixture array merge
Merge pull request #197 from fooman/load-shared-class-fixtures-before-methods2

Load shared class fixtures before methods
Merge pull request #174 from Schrank/dev

Add `replace` statement to composer.json
Merge pull request #207 from jzahedieh/jzahedieh/fix-204

fixes #204 getModelInstance() object to string
Merge pull request #180 from AOEmedia/feature/group_annotation_179

#179: Enabling group annotation on data provider
Strict compliance with EE 1.14.01 and CE 1.9.0.1
Merge pull request #216 from chernjie/getBaseUrl

Strict compliance with EE 1.14.01 and CE 1.9.0.1
Make more friendly error reporting on fixture files collision in config values. Thank to @BlueAcorn