fix(pg-cdc): fix support for partitioned table

[KeXiangWang]

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

What's changed and what's your intention?

The bug is found by user.
The bug contains two symptom:

1. If the specified publication is created without publish_via_partition_root = true, the source/table creation will throw an error with message ERROR: relation "original_table" is already member of publication "rw_publication".
2. If the publication is created by RW, RW cannot get any data.

The root cause is the publish_via_partition_root = true. Only with this option, the wal of each parition will be published in the root table's publication.

The fix is inspired by https://groups.google.com/g/debezium/c/NroAVr2saxU/m/eSeS8hYXCwAJ

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

https://github.com/risingwavelabs/risingwave-docs/pull/2628

[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.}}

[KeXiangWang]

The fix in this PR works. However, due to a bug in sea-schema, CI fails. Their fix is here, which is included in 0.15.0.

The upgrading to 0.15.0 of sea-schema is non-trivial. Will create another PR to fix.

[StrikeW]

LGTM!