Core: Restore the interrupt status in JdbcCatalog.execute

[PDGGK]

JdbcCatalog has four InterruptedException handlers. Three of them restore the interrupt status before rethrowing; execute does not.

	restores
initializeCatalogTables (:227)	yes
updateSchemaIfRequired (:268)	yes
execute (:781)	no
fetch (:814)	yes

execute backs every write path — dropTable, renameTable, renameView, dropNamespace and the namespace property insert/update/delete — so a task cancelled while waiting for a pooled connection ends up with a thread whose interrupt status has been cleared by Object.wait. Anything downstream that polls Thread.interrupted() to decide whether to stop, including the executors Spark and Flink use to cancel work, sees a thread that was never interrupted.

The fix is the same one line the other three handlers already have.

Testing

TestJdbcCatalog.testExecuteRestoresInterruptStatus builds a catalog with clients=1, holds the single pooled connection from another thread through the existing @VisibleForTesting connectionPool() accessor, interrupts the test thread, and asserts that dropTable both throws UncheckedInterruptedException and leaves the interrupt status set. It fails on main with Expecting value to be true but was false and passes with this change. Two latches rather than sleeps, so there is no timing window.

One thing worth flagging for whoever reviews the test: it has to call dropTable(ident, false). The single-argument dropTable defaults to purge = true, which reads table metadata through fetch first — and fetch already restores the status, so the assertion would pass even without the fix. The same trap applies to dropNamespace and the property setters.

• :iceberg-core:test --tests "org.apache.iceberg.jdbc.*" — passes
• :iceberg-core:spotlessCheck — passes

[uros-b]

This assert has no .hasMessage(...) / .hasMessageContaining(...) assertion. Iceberg's checkstyle rule AssertThatThrownByWithMessageCheck requires a message check on every assertThatThrownBy chain.

[PDGGK]

Good catch, thanks — fixed in 85c9952, the assertion now chains .hasMessage("Interrupted in SQL command"), matching how the rest of this file asserts (listNamespaces at :203, listViews at :305).

That was my miss: I ran spotlessCheck locally but not checkstyleTest, so the rule never had a chance to fire. I confirmed it does catch it — removing the .hasMessage(...) again reproduces your finding exactly:

[ant:checkstyle] [ERROR] .../jdbc/TestJdbcCatalog.java:1335: assertThatThrownBy must include a message check like .hasMessage(...) [AssertThatThrownByWithMessageCheck]

:iceberg-core:checkstyleMain, :iceberg-core:checkstyleTest and the test itself are all green on the new head.