feat(iceberg): refine iceberg table column datatype and name.

[chenzl25]

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

What's changed and what's your intention?

• Tracking: Iceberg engine table #19418
• Previously, the iceberg engine table replaced the scan with the iceberg source in the binder, but it will make the batch query datatype different from the datatype defined in the table. This PR moves this replacement from the binder to the optimizer and casts iceberg datatype to risingwave datatype.
• Support those types that aren't supported in Iceberg (like jsonb, smallint, serial, and so on).
• Iceberg V3 spec use _row_id as a reserved column name for row lineage, so if the table without primary key, we can't use _row_id directly for iceberg, this PR change it to _risingwave_iceberg_row_id

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.

[fuyufjh]

LGTM

[fuyufjh]

Is there any other example?

I am think whether we should bail! if a column is not found in the Iceberg source and it's not _rw_timestamp

[chenzl25]

I think _rw_timestamp is the only one that would hit this branch.

I am think whether we should bail! if a column is not found in the Iceberg source and it's not _rw_timestamp

This is the planner's beginning, so we must select all columns from a table (including the _rw_timestamp) unless we move this conversion to the end of the optimizer (after column pruning).