feat(iceberg): change http client max connection for iceberg compaction

[chenzl25]

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

What's changed and what's your intention?

• fine tune the iceberg spark compaction config to avoid HTTP connection error like software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Timeout waiting for connection from pool.

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

[graphite-app]

This change removes the default storage catalog type behavior when catalog_type is None. This appears to be an unintentional breaking change that could impact existing configurations. Consider either:

1. Restoring the previous default behavior for the None case:

None => Ok(HashMap::from_iter([
    ("type".to_owned(), "hadoop".to_owned()),
    ("warehouse".to_owned(), config.common.warehouse_path.clone()?),
])),

2. Documenting this as an intentional breaking change and providing migration guidance for users

The choice depends on whether removing the default storage catalog type is intentional. If unintentional, option 1 is recommended to maintain backwards compatibility.

Spotted by Graphite Reviewer

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