Docs: Add SeaweedFS REST catalog and FileIO configuration examples

[chrislusf]

Adds SeaweedFS to the configuration docs in two places:

• A SeaweedFS entry under Common Integrations and Examples: SeaweedFS table buckets serve an Iceberg REST catalog for table metadata while the table bucket stores the table data as Parquet files behind the same S3 gateway, so one config block covers catalog and FileIO.
• A SeaweedFS section under FileIO next to the other S3-compatible stores, since plain SeaweedFS buckets work with the existing S3FileIO / PyArrowFileIO.

The example configuration is verified directly against PyIceberg 0.10.0 and the current SeaweedFS release with exactly the properties shown (no region needed): create_namespace, create_table, append, scan round trip, drop_table, drop_namespace. SeaweedFS also runs PyIceberg-based Iceberg CI suites on every pull request: https://github.com/seaweedfs/seaweedfs/tree/master/test/s3tables

[Copilot]

Pull request overview

Adds documentation examples for configuring PyIceberg to work with SeaweedFS, covering both S3-compatible FileIO settings and an Iceberg REST catalog configuration.

Changes:

• Added a SeaweedFS entry to the “Common Integrations and Examples” S3-compatible FileIO section.
• Added a SeaweedFS subsection under the REST catalog configuration examples.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that's incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions.

[github-actions]

This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.