fix(source): REFRESH SCHEMA shall keep INCLUDE pk for UPSERT

[xiangjinwu]

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

What's changed and what's your intention?

It is required that an UPSERT source (actually table) to INCLUDE key and use it as primary key. However, when REFRESH SCHEMA, the INCLUDEs are always lost, effectively resulting in UPSERT tables cannot evolve their schemas.

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.

[tabVersion]

thanks for the fix

[tabVersion]

no need to check the new schema meets expectation?

[xiangjinwu]

This is actually a no-op refresh. We refresh immediately after creation without any schema change. But yes it is always good to test more:

• schema meets expectation after refresh
• actual data meets schema after refresh (rather than panic due to mismatch)
• works for protobuf in addition to avro
• works for debezium in addition to plain or upsert