GEODE-6558: Add InternalDistributedSystem.Builder

[kirklund]

• Remove all but one constructor.
• Replace newInstance methods with InternalDistributedSystem.Builder.
• Replace newInstanceForTesting methods with
  InternalDistributedSystem.BuilderForTesting.
• Replace public static boolean var ALLOW_MULTIPLE_SYSTEMS with usage
  of Boolean.getBoolean(ALLOW_MULTIPLE_SYSTEMS_PROPERTY) in
  connectInternal.

Most code paths are using DistributedSystem.connect or
InternalDistributedSystem.connectInternal to construct a system.
connectInternal now uses InternalDistributedSystem.Builder.

Several tests are using InternalDistributedSystem.BuilderForTesting.

NOTES FOR REVIEWERS (PLEASE READ):

NOTE: this is NOT the final refactoring/change to InternalDistributedSystem involving the Builder. We need to make some changes to reconnect for Micrometer. We will also be injecting a Micrometer MeterRegistry into InternalDistributedSystem. And finally, I think we'll be looking into making connectInternal private and changing internal code paths to use the Builder instead of connectInternal. Then there would be two code paths to create a InternalDistributedSystem:

1. DistributedSystem.connect which would delegate to InternalDistributedSystem.Builder
2. InternalDistributedSystem.Builder which would be used from internal code paths such as InternalCacheBuilder and reconnect

ALSO: I'd love to delete BuilderForTesting and replace it with mocking in every test where that's possible.

Please review: @demery-pivotal @mhansonp

[kirklund]

We could probably merge the two Builders if we add setInitialize(boolean) which defaults to true. The tests that use BuilderForTesting are basically constructing an instance of InternalDistributedSystem which NEVER gets initialized.

[kirklund]

The StressNewTest jobs failed multiple runs of MultipleCacheJUnitTest.

[kirklund]

I had to fix both GEODE-6562 and GEODE-6565 to get this precheckin green. Those are the 2nd and 3rd commits in this PR.

[kirklund]

SecurityManagerLifecycleIntegrationTest failed due to changes in the PR.

[kirklund]

LuceneClientSecurityWithRegionCreatedBeforeIndexDUnitTest and LuceneClientSecurityDUnitTest both failed, possibly due to changes in this PR.

[kirklund]

I separated GEODE-6562 and GEODE-6565 out to their own PRs.

InternalDistributedSystemBuilderIntegrationTest uses security which revealed a Shiro ThreadLocal leak when a Cache is not created (GEODE-6565) -- this caused MultipleCacheJUnitTest to fail when run later in the same JVM.

Fixing GEODE-6565 (Shiro ThreadLocal leak) caused LuceneClientSecurityDUnitTest and subclass to fail because a test was trying to use gemfire.properties that are incompatible with what's specified in getDistributedSystemProperties which is overridden in the super class.

[kirklund]

DistributedTest failure is an unrelated flaky failure in ClientServerTransactionFailoverDistributedTest

[moleske]

We'll merge those two builders in a future commit