fix - ReconnectToWriterHandler success flag by fixing isCurrentHostWriter()(#323)

Fix isCurrentHostWrite() which the ReconnectToWriterHandler success flag uses. Added more checks on host aliases fields to make it more robust

Author: aaronchung-bitquill

wrapper/src/main/java/software/amazon/jdbc/plugin/failover/ClusterAwareWriterFailoverHandler.java

@@ -293,14 +293,12 @@ public WriterFailoverResult call() {
     }
 
     private boolean isCurrentHostWriter(final List<HostSpec> latestTopology) {
-      final Set<String> currentAliases = this.originalWriterHost.getAliases();
       final HostSpec latestWriter = getWriter(latestTopology);
-      if (currentAliases == null) {
-        return false;
-      }
-      final Set<String> latestWriterAliases = latestWriter.getAliases();
+      final Set<String> latestWriterAllAliases = latestWriter.asAliases();
+      final Set<String> currentAliases = this.originalWriterHost.getAliases();
 
-      return latestWriterAliases.stream().anyMatch(currentAliases::contains);
+      return (currentAliases != null)
+          && (latestWriterAllAliases.stream().anyMatch(currentAliases::contains));
     }
   }
 

wrapper/src/main/java/software/amazon/jdbc/plugin/failover/FailoverConnectionPlugin.java

@@ -797,5 +797,4 @@ public Connection connect(
 
     return conn;
   }
-
 }