feat(cdc): support more metadata columns for MySQL, PG and MongoDB

[StrikeW]

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

What's changed and what's your intention?

Support more metadata columns for cdc table

• database_name, schema_name, table_name for PG and MySQL
• collection_name for MongoDB

Example:

CREATE TABLE person (
    id int,
    name varchar,
    email_address varchar,
    credit_card varchar,
    city varchar,
    PRIMARY KEY (id)
) INCLUDE TIMESTAMP AS commit_ts
INCLUDE DATABASE_NAME as database_name
INCLUDE SCHEMA_NAME as schema_name
INCLUDE TABLE_NAME as table_name
FROM pg_source TABLE 'public.person';

close #16654

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 more metadata columns for cdc table

• database_name, schema_name, table_name for PG and MySQL
• collection_name for MongoDB

[BugenZhao]

Since they're all empty messages, can we use the same message type instead? Or directly use google.protobuf.Empty?

[tabVersion]

IIRC, prost has some trouble with google well-known types.
& I use message structs for future extensibility on the column def, such as

message AdditionalColumnHeader {
  string inner_field = 1;
  data.DataType data_type = 2;
}

we won't want to handle the changes inside the catalog in the future.

[StrikeW]

message AdditionalColumn {
  oneof column_type {
    AdditionalColumnKey key = 1;
    AdditionalColumnTimestamp timestamp = 2;
    AdditionalColumnPartition partition = 3;
    AdditionalColumnOffset offset = 4;
    AdditionalColumnHeader header_inner = 5;
    AdditionalColumnFilename filename = 6;
    AdditionalColumnHeaders headers = 7;
  }
}

I think we need different message type for the oneof.

[tabVersion]

the impl LGTM, just to confirm cdc source does not need the additional column to maintain its states so no need for compatible code?

[StrikeW]

the impl LGTM, just to confirm cdc source does not need the additional column to maintain its states so no need for compatible code?

No need compatible code for cdc sources and tables defined in previous version. User need to recreate their source or table to get the metadata column.

[hzxa21]

Rest LGTM