refactor(frontend): generate replace plan without relying on definition

[BugenZhao]

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

What's changed and what's your intention?

Note: the diff can be outdated due to ongoing prerequisite refactoring.

We used to rely on the definition when re-planning the table for purposes like schema change or sink-into-table. However, maintaining column definitions can be hard, especially for the schemas resolved from registry.

This PR is a attempt to generate replace plan without relying on persisted definition, but directly retrieve necessary info from the internal representation (TableCatalog).

To accomplish this, we need to refactor the procedure for generating a plan from a CREATE TABLE SQL statement, so that we can reuse as much code as possible when it comes to generating a plan from an existing Table.

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

• My PR needs documentation updates.

Release note

[BugenZhao]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• refactor(frontend): generate replace plan without relying on definition #19866 👈 (View in Graphite)
• refactor(frontend): rearrange column binding steps in create table handler #19917
• refactor(frontend): merge steps for resolving on-conflict behavior in create table handler #19916
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.