Take updated dependencies

[ctz]

Notably this means rustls_platform_server_cert_verifier_with_provider can now return NULL. Avoiding that would mean using an out param and returning a rustls_result, but would be a major version bump. Thoughts?

(I checked and curl uses rustls_platform_server_cert_verifier and is therefore suitably fallible.)

[djc]

Notably this means rustls_platform_server_cert_verifier_with_provider can now return NULL. Avoiding that would mean using an out param and returning a rustls_result, but would be a major version bump. Thoughts?

Probably not worth doing a major bump for? Do we have a deprecation mechanism here? Stick with 0.5 until rustls 0.24 comes out?

[cpu]

Probably not worth doing a major bump for?

Yeah, probably not, but the README's ABI stability claims mean consumers that take our .so need to treat every release as a major bump. I'd personally be inclined to wait for more changes to pile up in main to do any kind of release (or revisiting if there's an explicit request from downstream).

Do we have a deprecation mechanism here?

I think cbindgen supports translating #[deprecated] into __attribute__((deprecated)) annotations in the .h if that's what you meant 🤔

[ctz]

I think cbindgen supports translating #[deprecated] into __attribute__((deprecated)) annotations in the .h if that's what you meant 🤔

Added a commit to enable this. Then I've added rustls_platform_server_cert_verifier_try_with_provider (not loving that name, suggestions welcome) and used it as justification to make rustls_platform_server_cert_verifier_with_provider deprecated.