feat: Add RESTscan Planning Endpoints and config

[geruh]

related to #2775

Rationale for this change

This PR adds some of the rest scanning endpoints needed for the synchronous scan planning And the configuration property used to determine scan planning support.

Aligning with the java implementation in apache/iceberg#13400.

Usage

catalog = RestCatalog(
 "the-best-rest-catalog", uri="http://127.0.0.1:8181", **{"rest.scan-planning.enabled": "true"},
)

Ideally we only would want to use rest scan planning if the catalog is capable. I remember there was a PR open for this at one point but can't seem to find it.

Are these changes tested?

Are there any user-facing changes?

new property to configure scanning

[kevinjqliu]

Thanks! Here are the corresponding IRC spec entries.

• namespaces/{namespace}/tables/{table}/plan
• namespaces/{namespace}/tables/{table}/tasks

Looks like rest-scan-planning-enabled is a server-side config. Should we check /v1/config response to see if the endpoints are supported by the catalog?

[kevinjqliu]

looks like rest-scan-planning-enabled is a catalog server config
https://github.com/apache/iceberg/blob/05998edb8808ae21739072cca17b621925a2081a/core/src/main/java/org/apache/iceberg/rest/RESTCatalogProperties.java#L40-L41

[kevinjqliu]

i dug into the use of rest-scan-planning-enabled, its actually not a catalog server config.
RESTSessionCatalog is the catalog client, and rest-scan-planning-enabled is used along with the checking whether the specific scan planning endpoint is advertised by the server.

https://github.com/apache/iceberg/blob/05998edb8808ae21739072cca17b621925a2081a/core/src/main/java/org/apache/iceberg/rest/RESTSessionCatalog.java#L275-L279
https://github.com/apache/iceberg/blob/05998edb8808ae21739072cca17b621925a2081a/core/src/main/java/org/apache/iceberg/rest/RESTSessionCatalog.java#L510

[geruh]

Looks like rest-scan-planning-enabled is a server-side config. Should we check /v1/config response to see if the endpoints are supported by the catalog?

Yes, I rememebr there was an open PR for the endpoints capability but haven't been able to find it. I'll probably raise a PR to add the endpoints logic. Furthermore, this is currently based off of the merged code in main.

[kevinjqliu]

after looking at the java client implementation, this makes sense to me! This PR follows the same PR here

We should also gate on the endpoint's existence but we can address that as a follow up.

[kevinjqliu]

Created an issue for reading /v1/config's endpoint #2847

[kevinjqliu]

LGTM!