test(ci): switch all tests to sql backend

[yezizp2012]

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

What's changed and what's your intention?

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.

[kwannoel]

Hi, before deprecating etcd backend, could we still keep their tests in main-cron still? Some users may continue using it and we won't deprecate etcd, at least in 2.0 I suppose.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9425213	Triggered	Generic Password	d0c1525	e2e_test/source/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	d0c1525	e2e_test/source/tvf/postgres_query.slt	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[yezizp2012]

updates:
There's only one flaky test in end-to-end source test when running e2e_test/source/basic/kafka.slt . Meta will encounter Failed to acquire connection from pool: Connection pool timed out as follows (https://buildkite.com/risingwavelabs/pull-request/builds/59508#019274d8-9f15-4d75-aab9-d2d9c9678d06):

2024-10-10T05:31:58.00352696Z  WARN risingwave_meta::controller::cluster: Failed to load expire worker info from db error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:31:58.003630889Z  WARN risingwave_meta::hummock: Vacuum metadata error error=Hummock error: failed to access meta store: Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:32:28.005092227Z  WARN risingwave_meta::rpc::metrics: fail to list worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:32:28.005118661Z  WARN risingwave_meta::rpc::metrics: fail to count worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:32:58.006758545Z  WARN risingwave_meta::controller::cluster: Failed to load expire worker info from db error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:33:28.008841941Z  WARN risingwave_meta::rpc::metrics: fail to count worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:33:28.008934887Z  WARN risingwave_meta::rpc::metrics: fail to list worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:33:58.010520665Z  WARN risingwave_meta::controller::cluster: Failed to load expire worker info from db error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:33:58.010616525Z  WARN risingwave_meta::hummock: Vacuum metadata error error=Hummock error: failed to access meta store: Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:34:28.011121148Z  WARN risingwave_meta::rpc::metrics: fail to count worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:34:28.011150804Z  WARN risingwave_meta::rpc::metrics: fail to list worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:34:58.012202046Z  WARN risingwave_meta::controller::cluster: Failed to load expire worker info from db error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:35:28.013878678Z  WARN risingwave_meta::rpc::metrics: fail to count worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:35:28.013962782Z  WARN risingwave_meta::rpc::metrics: fail to list worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:35:58.015341782Z  WARN risingwave_meta::controller::cluster: Failed to load expire worker info from db error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:35:58.015431101Z  WARN risingwave_meta::hummock: Vacuum metadata error error=Hummock error: failed to access meta store: Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:36:28.016727587Z  WARN risingwave_meta::rpc::metrics: fail to count worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:36:28.016763508Z  WARN risingwave_meta::rpc::metrics: fail to list worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:36:58.018054737Z  WARN risingwave_meta::controller::cluster: Failed to load expire worker info from db error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:37:28.019971563Z  WARN risingwave_meta::rpc::metrics: fail to list worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:37:28.019991183Z  WARN risingwave_meta::rpc::metrics: fail to count worker node error=Failed to acquire connection from pool: Connection pool timed out
2024-10-10T05:37:58.021876732Z  WARN risingwave_meta::controller::cluster: Failed to load expire worker info from db error=Failed to acquire connection from pool: Connection pool timed out

I'm still investigating. Should be fixed by #18885 .