Fix interrupt handling (#272)

## Changes
Current implementation does not work well when client interrupts a
thread where SDK code is running. Once interrupted, the logic continues
to run till the timeout (default 20mins) without sleeping at all. Each
time thread.sleep is called, it throws interrupt exception and this
results in calling the status API continuously without delay.

The PR is changing the handling to throw DatabricksException when the
thread is interrupted so that clients can stop the processing and handle
the exception as they wish.

## Tests
All unit tests are successful.

Author: avijeet95

.codegen/api.java.tmpl

@@ -96,6 +96,7 @@ public class {{.PascalName}}API {
             Thread.sleep((long) (sleep * 1000L + Math.random() * 1000));
         } catch (InterruptedException e) {
             Thread.currentThread().interrupt();
+            throw new DatabricksException("Current thread was interrupted", e);
         }
         attempt++;
     }

databricks-sdk-java/src/main/java/com/databricks/sdk/core/ApiClient.java

@@ -288,6 +288,7 @@ private Response executeInner(Request in) {
         timer.sleep(sleepMillis);
       } catch (InterruptedException ex) {
         Thread.currentThread().interrupt();
+        throw new DatabricksException("Current thread was interrupted", ex);
       }
     }
   }