fix: handle upsert json in prev versions

[tabVersion]

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

What's changed and what's your intention?

rewrite the catalog in compute node to match the include key as pattern, which is required in parser now.

rewrite condition:

• format upsert
• encode protobuf / encode avro / encode json
• column type bytea
• column name _rw_key

what to do

• edit the column's additional_column to AdditionalColumnType::Key

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]

incompatibility found:

• latest <=> v1.5: upsert json's _rw_key column is not labeled as key
• latest <=> v1.6.1 introduced in feat: only ingest key-ed value in additional header column #14628
  • in v1.6.1 additional_column_type = 9 in proto
  • in latest additional_column_type = 11 in proto

[fuyufjh]

LGTM.