feat(cdc): map upstream table schema automatically for cdc table

[StrikeW]

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

What's changed and what's your intention?

Automatically map the upstream table schema when creating a CDC table from mysql-cdc or postgres-cdc source.
We use the sea-schema crate to read the upstream schema.

• Add a ExternalTableImpl as an interface to read external table schema
• Some refactor to move mysql related code to mysql.rs.
• The * cannot be used with column definitions, for example create table t (v1 int, *) is prohibited.

Example:

dev=> create table supplier (*) from pg_source table 'public.supplier';
CREATE_TABLE
dev=> describe supplier;
       Name        |       Type        | Is Hidden | Description
-------------------+-------------------+-----------+-------------
 s_suppkey         | bigint            | false     |
 s_name            | character varying | false     |
 s_address         | character varying | false     |
 s_nationkey       | bigint            | false     |
 s_phone           | character varying | false     |
 s_acctbal         | numeric           | false     |
 s_comment         | character varying | false     |
 primary key       | s_suppkey         |           |
 distribution key  | s_suppkey         |           |
 table description | supplier          |           |
(10 rows)

close #16443

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.

[st1page]

Generally LGTM
It is recommended to split "code movement and refactoring" and "functional logic changes" into two separate PRs next time

[st1page]

Btw, Can you show an error message indicating that the database cannot be connected? I guess it would be very helpful for users to know that it is the frontend which need to be connected to the source database.

[StrikeW]

Btw, Can you show an error message indicating that the database cannot be connected? I guess it would be very helpful for users to know that it is the frontend which need to be connected to the source database.

Here is an example

dev=> create table mysql_all_types (*) from mysql_mydb table 'mydb.mysql_mydb';
ERROR:  Failed to run the query

Caused by these errors (recent errors listed first):
  1: connector error
  2: pool timed out while waiting for an open connection

[BugenZhao]

Can we adopt the new inline source style introduced in #16449?

[BugenZhao]

We can use ${RISEDEV_MYSQL_WITH_OPTIONS_COMMON}.

[BugenZhao]

Better to organize it under the new folder e2e_test/source_inline.

[StrikeW]

Will refactor in another pr.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 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.}}