feat(optimizer): add kafka scan operator

[chenzl25]

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

What's changed and what's your intention?

• Related issue: Refactor: refactor logical source for better batch optimization #16354
• Add a LogicalKafkaScan and BatchKafkaScan to avoid coupling too much with the Source operator.
• LogicalKafkaScan would be converted from LogiaclSource at the beginning of batch query optimization.
• BatchKafkaScan would still be converted to SourceNode by to_batch_prost_body to keep the modification minimum.

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.

[xxchan]

I like this. Thanks!

[xxchan]

Random thought: having output_exprs here is a little sign of copy-pasting to me. Maybe we can let LogicalSource::create directly return Project + Source. (Maybe not in this PR)

[chenzl25]

Agree. Let's do it later. output_exprs could easily introduce a potential bug, for example, the schema of the LogicalSource could be different from its core schema which is caught by the equivalent plan checking of the optimizer during the development of this PR.