Update the version of YugabyteDB JDBC Smart driver and correct the topology-keys.
This version has a fix for the case when a node specified in the connection string goes down while the workload is running, then the app does not fail. This was a case raised by @ddhodge
Also, corrected the topology-keys values. It should either be of the form cloud.region.zone or cloud.region.*. Latter includes all the zones in the region.
cloud.region.zoneorcloud.region.*. Latter includes all the zones in the region.