Once cryptography minimal version is 41, do some relevant cleanup

[itamarst]

Follow-up to #1202:

Once cryptography v40 is no longer supported, OpenSSL.SSL can expose X509_V_* constants unconditionally.

[h-vetinari]

This has actually become relevant now that cryptography 41.0.0 has been released, and is (nominally?) incompatible with the metadata in this package, which forces the constraint solver (of conda) into weird contortions that end up picking a very old pyopenssl that's not compatible with OpenSSL 3 for example.

Could we have a new release for pyopenssl, or alternatively, is it safe to remove the <41 cap in the dependency metadata?

CC @alex @reaperhulk @hmaarrfk

[reaperhulk]

We're doing a release that raises the cap momentarily (a later release will raise the minimum).

[h-vetinari]

Thanks, that's great to hear!

(I realised too late that this issue was for once the minimum is 41.x, sorry)

[facutuesca]

This issue was created at a point where the linked PR (#1202) conditionally exposed the x509_V_* constants according to the available capabilities. However, before merge that conditional ended up being removed (source). The reason for that was that the problematic cryptography versions that required that conditional were blacklisted in setup.py, so the conditional was no longer needed.

So this issue is already fixed (the constants are already exposed unconditionally). And the setup.py blacklisting is already removed since the minimum cryptography version is at 41.0.0

cc @mhils @reaperhulk