Extract resolveModelAndIdentifier logic to it's own service

Those updates are needed to make it possible for https://github.com/stephpy/TimelineBundle/issues/133
* added a ```ComponentDataResolverInterface``` 
* added a ```ResolveComponentDataException```
 * When not able to resolve the model and identifier an exception should be thrown
 * The current code  had logic exceptions, invalid argument exceptions 
 * To make it so the interface can tell to thrown an specific exception I added a custom one
* added method ```setComponentDataResolver``` and ```getComponentDataResolver``` to the abstract manager (adding constructor arguments is a BC break)
* added an exception class ```ResolveComponentDataException```
* added ```BasicComponentDataResolver``` which does the same logic as ```resolveModelAndIdentifier ``` for redis
* modified the ```resolveModelAndIdentifier ``` method for the redis action manager so it uses the ```BasicComponentDataResolver```
* updated the ```ServiceLocator```
* added identical methods ```resolveModelAndIdentifier``` ```getComponentFromResolvedComponentData```between all the action managers to the abstract action manager
* Added tests
 * Redis ActionManager ``findOrCreateComponent``` 
 * BasicComponentDataResolver
 * ResolveComponentModelIdentifier

#### Changed logic:
- The action manager gets populated by a Component Data resolver by ```setComponentDataResolver``
- The method ```resolveModelAndIdentifier``` (used by ```CreateComponent``` uses this service) 
- The logic has been extracted ouf of the method ```resolveModelAndIdentifier``` into it's own service ```BasicComponentDataResolver```