tls: enable session ticket cache by default

[dkropachev]

Fixes: #392
RFC: https://datatracker.ietf.org/doc/html/rfc5077

Enables TLS session ticket cache by default.

[mykaul]

But do we know how to use it when connecting to a different shard (in same node though) ?

[dkropachev]

But do we know how to use it when connecting to a different shard (in same node though) ?

Cache is going to be shared not only between shard connections, but also between any connections created by any session from the same ClusterConfig

[mykaul]

But do we know how to use it when connecting to a different shard (in same node though) ?

Cache is going to be shared not only between shard connections, but also between any connections created by any session from the same ClusterConfig

That's useless (I think), as the session ticket is not shared among nodes, just among shards within the same node.

[dkropachev]

But do we know how to use it when connecting to a different shard (in same node though) ?

Cache is going to be shared not only between shard connections, but also between any connections created by any session from the same ClusterConfig

That's useless (I think), as the session ticket is not shared among nodes, just among shards within the same node.

It comes naturally from how driver works with tls.Config and golang internals.