Bump rustls from 0.22.1 to 0.23.18

[TCeason]

Suggest bump, in databend ci:

cargo audit --db ./target/advisory-db
==> build-tool using image runner/build-tool:dev-nightly-2024-07-02
Fetching advisory database from [https://github.com/RustSec/advisory-db.git](https://github.com/RustSec/advisory-db.git%60)
Loaded 688 security advisories (from ./target/advisory-db)
Updating crates.io index
Scanning Cargo.lock for vulnerabilities (1349 crate dependencies)
Crate: rustls
Version: 0.22.4
Title: rustls network-reachable panic in Acceptor::accept
Date: 2024-11-22
ID: RUSTSEC-2024-0399
URL: https://rustsec.org/advisories/RUSTSEC-2024-0399
Solution: Upgrade to >=0.23.18
Dependency tree:
rustls 0.22.4
├── tokio-rustls 0.25.0
│ └── opensrv-mysql 0.7.0
│ └── databend-query 0.1.0
│ ├── databend-enterprise-query 0.1.0
│ │ └── databend-binaries 0.1.0
│ └── databend-binaries 0.1.0
├── msql-srv 0.11.0
│ └── databend-sqllogictests 0.1.0
└── databend-query 0.1.0

[TCeason]

Hi @jonhoo Please review this pr.

[mjgarton]

I personally welcome this change, but I think this is a breaking change (for callers that also interact directly with rustls), so probably the msql-srv version in Cargo.toml needs bumping?

[TCeason]

I personally welcome this change, but I think this is a breaking change (for callers that also interact directly with rustls), so probably the msql-srv version in Cargo.toml needs bumping?

I see tokio-rustls it use ring feature.

[jonhoo]

Since I don't use this crate any more myself, I'm ending up with very little time to actually devote to its upkeep. If either of you are actively using it, would you be interested in stepping up to maintaining it?