Jaxb classes are incorrectly serialized when both the kie-remote-client and kie-remote-service modules are available in the classpath

The refactoring done to give the `kie-remote-client` artifact a lighter dependency footprint, added faulty logic to the `JaxbSerializationProvider` class that adds classes to the `JAXBContext` instance used.

This logic first tries to create the client side classes (generated `org.kie.remote.jaxb.gen` classes) and only if those classes are not available on the classpath, adds the server side classes.

However, if both `kie-remote-client` and `kie-remote-service` are on the classpath, this logic will cause a problem somewhere.

This jira is for the fix in the logic that fixes this problem.