feat(mysql-cdc): support mysql source capture multiple databases

[StrikeW]

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

What's changed and what's your intention?

As title.
User can ingest table in different database by specifying multiple database names in the database.name field.

create source mysql_source with (
 connector = 'mysql-cdc',
 ...
 database.name = 'mydb,kdb'
);

create table t1 (*) from mysql_source table "kdb.t1";

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

• support capturing multiple databases for mysql cdc source

[gitguardian]

⚠️ GitGuardian has uncovered 3 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	0aa5af1	risedev.yml	View secret
9425213	Triggered	Generic Password	0aa5af1	e2e_test/source_inline/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	0aa5af1	e2e_test/source_inline/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.}

[KeXiangWang]

LGTM

[KeXiangWang]

Should we then delete the MYSQL branch in ValidatorUtils.getJdbcUrl?

[KeXiangWang]

String.format("MySQL database '%s' doesn't exist", dbName.trim()));