ssl_options is broken on Python3.12

[fruch]

This older style of no using ssl context, is broken on 3.26.4

Seems like it's was mostly addressed already in up stream:

datastax#1191

Maybe we should deprecated completely at our end ?
Or just sync with 3.29.0 to get it ?

[fruch]

@avelanarius @Lorak-mmk, are we planning syncing with upstream 3.29.0, any time soon ?

or we'll need to backport the fix for this one manually ?

[avelanarius]

Is this issue urgent to fix?

I'd rather plan syncing with upstream to the next sprint (~start of February) since we already have a lot of stuff planned around Rust Driver.

[fruch]

Is this issue urgent to fix?

I'd rather plan syncing with upstream to the next sprint (~start of February) since we already have a lot of stuff planned around Rust Driver.

I can't tell exactly who is using ssl_options, but if they gonna move into python 3.12, it would stop working...

I've hit it in dtest in few tests, that wasn't using ssl_context, but I don't have anymore information beyond that

I've fixed the dtest to stop using it, so I can move to python 3.12

[fruch]

at least scylla tests are using only ssl_context
https://github.com/search?q=repo%3Ascylladb%2Fscylladb+ssl_context&type=code