Fix should_send_down_notifications_after_init_when_contact_points_are_down for 3.11.4.0

Seen most recently during 6.2 tests.
Session in this test method is mistakenly initialized with only 1 node, making following
assertion incorrect. Newest 3.x driver has the same fix already done.

Closes #47.

Author: Bouncheck

versions/scylla/3.11.4.0/ignore.yaml

@@ -0,0 +1,2 @@
+tests:
+  -

versions/scylla/3.11.4.0/patch

@@ -0,0 +1,22 @@
+diff --git a/driver-core/src/test/java/com/datastax/driver/core/LoadBalancingPolicyBootstrapTest.java b/driver-core/src/test/java/com/datastax/driver/core/LoadBalancingPolicyBootstrapTest.java
+index 09f8bf8edb..4f01cb47a6 100644
+--- a/driver-core/src/test/java/com/datastax/driver/core/LoadBalancingPolicyBootstrapTest.java
++++ b/driver-core/src/test/java/com/datastax/driver/core/LoadBalancingPolicyBootstrapTest.java
+@@ -104,8 +104,16 @@ public class LoadBalancingPolicyBootstrapTest extends CCMTestsSupport {
+       ccm().stop(nodeToStop);
+       ccm().waitForDown(nodeToStop);
+ 
++      // usually only one contact point is used to build the test cluster
++      // here we explicitly add both endpoints so we can test load
++      // balancing initial connection when the first connection point is down
+       HistoryPolicy policy = new HistoryPolicy(new RoundRobinPolicy());
+-      Cluster cluster = register(createClusterBuilder().withLoadBalancingPolicy(policy).build());
++      Cluster cluster =
++          register(
++              createClusterBuilder()
++                  .addContactPoints(ccm().getContactPoints().get(1))
++                  .withLoadBalancingPolicy(policy)
++                  .build());
+ 
+       try {
+         cluster.init();