Force using common classloader as context classloader when calling Jersey REST client.
The original cause is still there - the Jersey REST client classes are in an OSGi bundle classloader which is not accessible from the current context classloader. I couldn't manage to fix this so that OSGi automatically wires those classloaders. That would be even better, because this boiler plate code wouldn't be needed and all would work automatically, and not only in these places but everywhere in Admin Console.
Fixes #24619.
Force using common classloader as context classloader when calling Jersey REST client.
The original cause is still there - the Jersey REST client classes are in an OSGi bundle classloader which is not accessible from the current context classloader. I couldn't manage to fix this so that OSGi automatically wires those classloaders. That would be even better, because this boiler plate code wouldn't be needed and all would work automatically, and not only in these places but everywhere in Admin Console.