Redesign the LibClassLoader to load connector and its dependencies

[arunans23]

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

This PR reverts the following PRs and add a new implementation for the LibClassLoader.

• Revert Improve LibClassLoader to recursively add jars to classpath #2311
• Reverts Fix classloader loader issue when adding car file with class mediators #2293
• Revert Fix classloader loader issue when adding connector zip with libs #2290
• Revert Improve connector dependency deployment #2239

Improvement commits

• Redesign the LibClassLoader to load connector and its dependencies

Earlier design

As per the above design, one class loader is used per capp to load the class mediators, connectors and its dependencies. But this raises an issue where two connectors or its dependencies can have the same class name and package name which can cause a confusion when loading a specific class.

Hence the following design is proposed.

New design

Here a classloader is used for each connector. All the connector specific dependencies will be loaded to that particular class loader. This will prevent two connectors having similar classes getting added to the same classloader. The class mediators will be loaded to individual class loaders as before.