chore(madsim,deps): use patched sqlx managed by the madsim-rs organization instead of a personal repository

[kwannoel]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

We use patched sqlx from the madsim fork, instead of the one in my personal fork of sqlx.

Please review the changes in that fork prior to reviewing this PR.

This accomplishes two things:

1. Let the Madsim Org manage the fork. We can have PR reviews each time we rebase the patch.
2. Inside the fork will adopt a rebase workflow, and continually patch for madsim on top of the tagged commit corresponding to the latest sqlx version.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[hzxa21]

Is the downgrade here expected?

[kwannoel]

Reverted it. Seems really strange. Each time I run cargo update sqlx, it keeps updating this dependency as well, for some reason.

[BugenZhao]

We use patched sqlx from the risingwave fork: risingwavelabs/sqlx#1, instead of the one in my personal fork of sqlx.

As the changes are solely to make sqlx compatible with madsim, I slightly prefer keeping it maintained under madsim-rs, especially when considering that we all have write permissions to madsim-rs now.

Otherwise, should we also move other forks, like tonic, rdkafka, tokio-postgres or even tokio-stream into risingwavelabs org?

[kwannoel]

We use patched sqlx from the risingwave fork: risingwavelabs/sqlx#1, instead of the one in my personal fork of sqlx.

As the changes are solely to make sqlx compatible with madsim, I slightly prefer keeping it maintained under madsim-rs, especially when considering that we all have write permissions to madsim-rs now.

Otherwise, should we also move other forks, like tonic, rdkafka, tokio-postgres or even tokio-stream into risingwavelabs org?

Done. madsim-rs/sqlx#3.

[kwannoel]

I pushed it to madsim, but didn't update it here 🤦 . Regardless they are using the same commit.

I will update this later when bumping sqlx to 0.8.2: #19145