Elastic type names are not distinct for same name domain classes in different packages

In ran into this issue while using a local checkout of the plugin. My app has a ```my.package.User``` and ```my.package.Tag``` domain class just as the plugin has. When I persist instances of my users, bulk index items are never removed from the operation batch list, because ```test.User``` is assumed to be the domain class' type, effectively resulting in an endless loop, as items are pushed again and again.

Mapping the domain class to the Elastic type name only takes the simple class name into account. ```my.package.User``` and ```test.User``` are both mapped to ```user```.

This pull request is fixing this by using the fully-qualified class name, e.g. ```my.package.user``` and ```test.user```.