Serializee is a managed class and we should use always an injected instance

This change breaks compatibility because change constructor signature. Of course only for users who extends serialization internal classes. No public API was changed.

But this change is really necessary because we are not using managed `Serializee` for all classes. There are some places that uses a non managed instance that isn't the same instance in the places that uses managed instance.
@Turini I think that is better to leave as is, because this class is vetoed, and receives instances from `VRaptorXStream` that is vetoed too, that receives instances from `XStreamBuilderImpl`. I tried to take this change, and a lot of classes will be changed its contructors to receive `Instance<>` instead of the object.

And more: there are some classes used in tests like `MockSerializationResult`, forcing users to rewrite their classes when migrate.

What you think to leave as is, with `Supplier`? Do you want I send to you a patch with changes?