GEODE-8466: Introduction of ClassLoaderService

[kohlmu-pivotal]

Introduction of ClassLoaderService as replacement for the direct feature usage of ClassLoader and ClassLoaderPath

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

• Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

• Has your PR been rebased against the latest commit within the target branch (typically develop)?

• Is your initial contribution a single, squashed commit?

• Does gradlew build run cleanly?

• Have you written or updated unit tests to verify your changes?

• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:

Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.

[lgtm-com]

This pull request introduces 3 alerts and fixes 1 when merging d802284 into 505eb3a - view on LGTM.com

new alerts:

• 2 for Potential input resource leak
• 1 for Use of a broken or risky cryptographic algorithm

fixed alerts:

• 1 for Use of a broken or risky cryptographic algorithm

[lgtm-com]

This pull request introduces 3 alerts and fixes 1 when merging 6f10c15 into 505eb3a - view on LGTM.com

new alerts:

• 2 for Potential input resource leak
• 1 for Use of a broken or risky cryptographic algorithm

fixed alerts:

• 1 for Use of a broken or risky cryptographic algorithm

[lgtm-com]

This pull request introduces 3 alerts and fixes 1 when merging 382bd52 into 505eb3a - view on LGTM.com

new alerts:

• 2 for Potential input resource leak
• 1 for Use of a broken or risky cryptographic algorithm

fixed alerts:

• 1 for Use of a broken or risky cryptographic algorithm

[lgtm-com]

This pull request introduces 3 alerts and fixes 1 when merging 312d7d4 into 505eb3a - view on LGTM.com

new alerts:

• 2 for Potential input resource leak
• 1 for Use of a broken or risky cryptographic algorithm

fixed alerts:

• 1 for Use of a broken or risky cryptographic algorithm

[lgtm-com]

This pull request introduces 3 alerts and fixes 1 when merging 3fa823a into 505eb3a - view on LGTM.com

new alerts:

• 2 for Potential input resource leak
• 1 for Use of a broken or risky cryptographic algorithm

fixed alerts:

• 1 for Use of a broken or risky cryptographic algorithm

[lgtm-com]

This pull request introduces 3 alerts and fixes 1 when merging ddb08eb into 4624211 - view on LGTM.com

new alerts:

• 2 for Potential input resource leak
• 1 for Use of a broken or risky cryptographic algorithm

fixed alerts:

• 1 for Use of a broken or risky cryptographic algorithm

[lgtm-com]

This pull request introduces 3 alerts and fixes 1 when merging 846309e into 70b1ee8 - view on LGTM.com

new alerts:

• 2 for Potential input resource leak
• 1 for Use of a broken or risky cryptographic algorithm

fixed alerts:

• 1 for Use of a broken or risky cryptographic algorithm

[lgtm-com]

This pull request introduces 3 alerts and fixes 1 when merging a74cbad into 70b1ee8 - view on LGTM.com

new alerts:

• 2 for Potential input resource leak
• 1 for Use of a broken or risky cryptographic algorithm

fixed alerts:

• 1 for Use of a broken or risky cryptographic algorithm

[onichols-pivotal]

This PR has been inactive for some while, can it be closed?