Bad Behaviour in New v1.2.0 Release?

### What version of Cassandra are you using?
ScyllaDB 5.0 (but same all the way down to 4.0 at each major point release, which is as far as we test back)

### What version of Gocql are you using?
Latest/1.20

### What version of Go are you using?
1.18

### What did you do?
Our CI scripts wait for port 9042 to open, then start creating the test databases. It seems that in CI the new release fails completely, consistently (regardless of adding extra delays/sleeps - even many minutes). The code fails during startup completely. However, if we go back to the prior release or switch over to the ScyllaDB fork specifically, the issue goes away.

### What did you expect to see?
Our CI tests should pass as usual.

### What did you see instead?

```
=== RUN TestUpsertModel
operations_model_test.go:20: Using test keyspace: unittest_model_manager_1657252471641166683
operations_model_test.go:30:
Error Trace: operations_model_test.go:30
Error: Expected nil, but got: &fmt.wrapError{msg:"no connections were made when creating the session", err:(*fmt.wrapError)(0xc00048b1c0)}
```

Reproduce the failure in CI with Go 1.18, gocql 1.20, and ScyllaDB 5.0, then inspect operations_model_test.go around lines 20 and 30 and the session-startup path it exercises. Done means the session connects after port 9042 opens and TestUpsertModel passes with the new release, as it does with the prior release or ScyllaDB fork.

Written by the indexing model from the issue text.