Fix StreamingChunkDownloadTask to catch RuntimeException (parity with #1302)

PR #1302 fixed ChunkLinkDownloadService (legacy RemoteChunkProvider path)
to catch DatabricksError (extends RuntimeException) when the server
returns HTTP 404 for expired results. StreamingChunkDownloadTask had the
same gap — only caught IOException | SQLException, letting DatabricksError
escape uncaught and leaving the chunk in a bad state.

Widen catch to IOException | SQLException | RuntimeException so expired
result errors are retried properly.

Co-authored-by: Isaac
Signed-off-by: Gopal Lal <gopal.lal@databricks.com>

Author: gopalldb

src/main/java/com/databricks/jdbc/api/impl/arrow/StreamingChunkDownloadTask.java

@@ -64,7 +64,7 @@ public Void call() throws DatabricksSQLException {
 
           LOGGER.debug("Successfully downloaded chunk {}", chunk.getChunkIndex());
 
-        } catch (IOException | SQLException e) {
+        } catch (IOException | SQLException | RuntimeException e) {
           retries++;
           if (retries >= MAX_RETRIES) {
             LOGGER.error(