Using JBoss Modules to implement classloader isolated jar deployment

Introduce Classloader isolation into Geode, to avoid the potential conflict of custom code dependencies, from deployed jars, and the dependencies of the Geode system.

This problem became evident when Geode was still dependent on Spring framework 4.3 and users wanted to deploy custom jars that used Spring framework 5. This caused many library version conflicts.

This problem is not limited to the usage of Spring in the system but to ANY dependent library that Geode and any potential custom jar would use.

The end goal is to have a system that is Classloader isolated and allows for the usage of libraries of different versions within Geode without any conflicts.

See RFC https://cwiki.apache.org/confluence/display/GEODE/ClassLoader+Isolation for further details