Extract resolveModelAndIdentifier logic to it's own service

This pull request requires the changes from https://github.com/stephpy/timeline/pull/27
The reason for this change is in https://github.com/stephpy/TimelineBundle/issues/133

### What was added/changed for the bundle
#### The action manager
* A new service  ```DoctrineComponentDataResolver``` is loaded into the action manager by calling ```setComponentDataResolver```. This contains the logic which was was previously in the method ```resolveModelAndIdentifier```.
* The method ```resolveModelAndIdentifier``` was changed to use this service.
* The method  ``AddRegistry `` was removed from the action manager
 * It was only used in the method  ```resolveModelAndIdentifier```
 * It is now in the ```DoctrineComponentDataResolver```
* The method ```resolveModelAndIdentifier```  is now identical between all the drivers (doctrine orm, odm, redis) and has been moved to the abstract action manager.

#### Compiler passes
* The compiler pass ```AddRegistryCompilerPass``` has been updated to load the doctrine managers into the ```DoctrineComponentDataResolver``` by calling ```AddRegistry```
* Added compiler pass ```AddComponentDataResolver``` to load the ComponentDataResolver into the action manager.

#### Tests
* ORM action manager:  ```createComponent ``` ```findOrCreateComponent```
* DoctrineComponentDataResolver 

#### Two new component data resolver services
* spy_timeline.resolve_component.doctrine
 * The default implementation. When trying to resolve the model and identifier, when the model is an object it tries to use doctrine to resolve the model class name and the identifier
* spy_timeline.resolve_component.basic
 * When trying to resolve the model and identifier, when the model is an object it uses the get_class php method for the model and the getId method in the object to retrieve the identifier.

#### Updates to the config
It is possible to define which component data resolver service you want to use. An section resolve_component is added to the config where you can define your resolver. It's now also possible to create your own service. It just has to implement ```ComponentDataResolverInterface```
 ```
resolve_component:
        resolver:   spy_timeline.resolve_component.doctrine #default one
 ```
About BC breaks: 
- Maybe for those who have overwritten the protected function ```resolveModelAndIdentifier```.  But changes to this function have been made in the past week already. 
- The method  ``AddRegistry `` was removed from the action manager. The code was only used  for ```resolveModelAndIdentifier```. Since we already got the objectmanager I see no reasons why one should have to rely on the manager registries being in the action manager.

The test fails because it relies on a pull request in the timeline which has not been merged yet. 
This pull request is ready for review.