Fix for wrong connection count on remote nodes

[HarshDaryani896]

Description
Issue: Even after setting CONNECTION_POOL_REMOTE_SIZE to zero, connections were getting created to remote nodes. Number of connections on REMOTE nodes were equal to Number of connections on LOCAL nodes.

On some investigation we found out that the private localDc variable of YugabyteDefaultLoadBalancingPolicy class [child class] was hiding the localDc variable of the BasicLoadBalancingPolicy class [parent class], due to which the driver was not properly identifying Local AND Remote nodes. It was considering all Up nodes as Local.

Fix
Removed the private localDc from YugabyteDefaultLoadBalancingPolicy and made the localDc variable in BasicLoadBalancingPolicy protected.
Also did this change for another private member variable of YugabyteDefaultLoadBalancingPolicy class: distanceReporter

Note
This PR also includes some formatting changes in PartitionAwarePolicy.java

Testing

1. Tested locally using a sample app to verify remote and local node connections.
2. nosqlbench test runs with different consistency level and local datacenter specifications has been done, and load routing behaviour is as expected.
3. Tests in ycql-4.x-tests repo: 7 Tests, 5 Passed, 2 Errors in TestDMLRoutingLocality(these occur with 4.15.0-yb-1 also).
4. Tests in Yugabyte-db repo: 13 Tests, all Passed.

[ashetkar]

Also, please run the formatting command and commit the changes

mvn com.coveo:fmt-maven-plugin:format

[kneeraj]

Should get a clean run of nosqlbench with correct routing behaviour before merging.

[HarshDaryani896]

Should get a clean run of nosqlbench with correct routing behaviour before merging.

@kneeraj nosqlbench run with different consistency level and local datacenter specifications has been done, and load routing behaviour is as expected. cc: @ashetkar

[ashetkar]

@HarshDaryani896 Let's get this PR cleaned of all the debugging logs and merge it, if we have successfully completed all the testing.
We can work on debugging logs on another branch.
Also, please mention the test case which was failing earlier but is fixed by your change, for reference.

[ashetkar]

Also, please add a log at debug/info 1) when metadata is refreshed and 2) when leader is not found for a particular tablet.

[kneeraj]

lgtm