Add rename_view to REST Catalog

[rambleraptor]

Rationale for this change

As part of #818, this adds rename_view support to the Iceberg REST Catalog.

The REST Catalog spec specifies that both rename_view and rename_table do not return anything. Currently, rename_table returns the table. I'm happy to change that API if we want, but it would technically be a breaking change.

Are these changes tested?

Added unit tests.

Are there any user-facing changes?

• Added rename_view support to Iceberg REST Catalog.

[rambleraptor]

@Fokko@kevinjqliu mind taking a look when you can? thanks!

[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 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.

[rambleraptor]

@geruh looks like you've been going through the View PRs. Mind taking a look at this one? Follows the others near-identically.

[rambleraptor]

@ebyhr can you take a look? You've been doing a lot of work around views lately.

[rambleraptor]

@kevinjqliu@Fokko@geruh mind taking a look? This will help with all of the View work that's been done.

[abnobdoss]

Looks good! The only concern I have is the point you highlighted in the PR description of the discrepancy between rename_table returning a Table but rename_view returning None. It sounds like the right fix would be to change rename_table to return None to be aligned to the spec. Since that is a breaking change I imagine we likely would have to wait till 1.0.0 to align those functions.

[rambleraptor]

I agree that rename_table should return None. I'm actually going to make an issue for us to track potential breaking changes for v1.0

[rambleraptor]

@kevinjqliu mind taking a look? This should be good to go!

[nhuantho]

self._split_identifier_for_json is still called twice per namespace.
I think we can move the payload after checking namespace_exists, for example

 source = self._split_identifier_for_json(from_identifier)
destination = self._split_identifier_for_json(to_identifier)
# Ensure that namespaces exist on source and destination.
source_namespace = source["namespace"]
if not self.namespace_exists(source_namespace):
raise NoSuchNamespaceError(f"Source namespace does not exist: {source_namespace}")
destination_namespace = destination["namespace"]
if not self.namespace_exists(destination_namespace):
raise NoSuchNamespaceError(f"Destination namespace does not exist: {destination_namespace}")
payload = {
"source": source,
"destination": destination,
}