[FEATURE REQUEST] Support endpoints field in the config endpoint

[danielhumanmod]

Description

As the endpoints field was introduced in Iceberg REST spec recently to describe the server capabilities in /v1/config, Polaris can align with this change by extending the catalog config API to include the endpoints field.

Fixes #316

Included Changes:

• Update rest-catalog-open-api.yaml config
• Add endpoints support in IcebergCatalogAdapter
• Extend ConfigResponse and ResourcePaths as a temp workaround before integrated with Iceberg 1.70

TODO
Since the latest changes related to endpoints are not yet released (currently at version 1.6.1) and are planned for release in 1.7.0, we need to replace the two extended classes with the Iceberg's implementations after the upgrade.
Related PR: apache/iceberg#10929

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• Documentation update
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• Hardware:
• Toolchain:
• SDK:

Checklist:

Please delete options that are not relevant.

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• If adding new functionality, I have discussed my implementation with the community using the linked GitHub issue

[eric-maynard]

Does it make sense to hold off until 1.7.0?

[danielhumanmod]

Yes, we will hold if off until 17.0 based on the discussion here: #316