Allow lazy register in versioning service

The versioning service accepts configuration for the implementing class. The class is loaded when the contribution is registered. That way, a custom extension is not loaded at startup, because it is deployed after the service itself.
The contribution should be loaded "lazy", that means only a string to be stored and the class loaded dynamically when required.