Core: Add View support for REST catalog

[nastra]

No description provided.

[nastra]

I've renamed this parameter to make the code slightly easier to understand, because we have a few cases in this method where we re-assign either the schema id or the view version id

[rdblue]

Minor: I think I pointed this out before and may have forgotten the answer, but shouldn't this be a consistent exception class every time?

[nastra]

I remember I replied to this but somehow can't find where it was.
The issue with the REST version is unfortunately that it fails with org.apache.iceberg.exceptions.BadRequestException: Malformed request: Invalid view version: Cannot add multiple queries for dialect trino because we're re-applying all changes to the Builder in CatalogHandlers.createView(...):

iceberg/core/src/main/java/org/apache/iceberg/rest/CatalogHandlers.java

Lines 424 to 429 in f076b4d

	request.viewVersion().representations().stream()
	.filter(SQLViewRepresentation.class::isInstance)
	.map(SQLViewRepresentation.class::cast)
	.forEach(r -> viewBuilder.withQuery(r.dialect(), r.sql()));
	View view = viewBuilder.create();

That IAE is then converted to a BadRequestException in

iceberg/core/src/main/java/org/apache/iceberg/rest/ErrorHandlers.java

Lines 204 to 205 in ace0b13

	case 400:
	throw new BadRequestException("Malformed request: %s", error.message());

So I think what we could do is to have

if (IllegalArgumentException.class.getSimpleName().equals(error.type())) {
        throw new IllegalArgumentException(error.message());
}

in the DefaultErrorHandler. Thoughts?

[rdblue]

I think this is nearly ready but the concurrent test case actually refreshes correctly and doesn't test the concurrent case with server-side retry and ID reassignment. I made a suggestion in the comment that I think will fix the test issue.

This will probably also require a flag in ViewCatalogTests for when server-side retry is possible like in table tests. If we're testing it correctly, then the InMemoryCatalog will fail.

[rdblue]

Thanks @nastra! Great to have this in.