feat(iceberg): support iceberg connection

[chenzl25]

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

What's changed and what's your intention?

• Related tracking: Connection #19637
• Support iceberg connection. Most of the iceberg properties could be specified in the iceberg connection except database.name and table.name.

Example:

CREATE CONNECTION CONN WITH (
    type = 'iceberg',
    catalog.name = 'demo',
    catalog.type = 'storage',
    warehouse.path = 's3a://hummock001/iceberg-data',
    s3.endpoint = 'http://127.0.0.1:9301',
    s3.region = 'us-east-1',
    s3.access.key = 'hummockadmin',
    s3.secret.key = 'hummockadmin'
);

statement ok
CREATE SINK sink1 from s1 WITH (
    connector = 'iceberg',
    type = 'upsert',
    database.name = 'demo_db',
    table.name = 'test_connection_table',
    connection = conn,
    create_table_if_not_exists = 'true',
    commit_checkpoint_interval = 1,
    primary_key = 'i1,i2',
);

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

• Support iceberg connection

[graphite-app]

There appears to be a stray iceberg_connection line at the end of this TOML file that should be removed. This line isn't valid TOML syntax and could interfere with proper file parsing.

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.

[tabVersion]

LGTM

[github-actions]

Hi, there.

📝 Telemetry Reminder:
If you're implementing this feature, please consider adding telemetry metrics to track its usage. This helps us understand how the feature is being used and improve it further.
You can find the function report_event of telemetry reporting in the following files. Feel free to ask questions if you need any guidance!

• src/frontend/src/telemetry.rs
• src/meta/src/telemetry.rs
• src/stream/src/telemetry.rs
• src/storage/compactor/src/telemetry.rs
  Or calling report_event_common (src/common/telemetry_event/src/lib.rs) as if finding it hard to implement.
  ✨ Thank you for your contribution to RisingWave! ✨

---

This is an automated comment created by the peaceiris/actions-label-commenter. Responding to the bot or mentioning it won't have any effect.