Upgrade SDK - to support discovery url on U2M (AWS and GCP flows) (#1011)

## Description
- This is to support Discovery URL for U2M AWS and GCP in OSS JDBC
databricks/databricks-sdk-java#505 (Note azure
is not supported as it has a different flow in OSS JDBC)

## Testing
Tested that discovery URL is being honored in U2M as well. Tested this
using the OSS JDBC with the following URL
1. Success flow test : 
```
String jdbcUrl =
        "jdbc:databricks://e2-dogfood.staging.cloud.databricks.com:443/default;transportMode=http;ssl=1;httpPath=/sql/1.0/warehouses/dd43ee29fedd958d;"
            + "AuthMech=11;Auth_Flow=2;LogLevel=6;UseThriftClient=0;EnableTokenCache=0;OIDCDiscoveryEndpoint=https://e2-dogfood.staging.cloud.databricks.com/oidc/.well-known/oauth-authorization-server";
```
2. Failure flow test : 
```
String jdbcUrl =
        "jdbc:databricks://e2-dogfood.staging.cloud.databricks.com:443/default;transportMode=http;ssl=1;httpPath=/sql/1.0/warehouses/dd43ee29fedd958d;"
            + "AuthMech=11;Auth_Flow=2;LogLevel=6;UseThriftClient=0;EnableTokenCache=0;OIDCDiscoveryEndpoint=https://google.com";
```

Also tested using GCP : 

```
"jdbc:databricks://6177827686947384.4.gcp.databricks.com:443/default;transportMode=http;ssl=1;EnableTokenCache=0;AuthMech=11;Auth_Flow=2;httpPath=/sql/1.0/warehouses/f5e97c8f8dfb56b5;OIDCDiscoveryEndpoint=https://6177827686947384.4.gcp.databricks.com/oidc/.well-known/oauth-authorization-server";
   
```

Author: samikshya-db

NEXT_CHANGELOG.md

@@ -13,9 +13,10 @@
 - Implement lazy/incremental fetching for columnar results when using Databricks JDBC in Thrift mode without Arrow support. The change modifies the behavior from buffering entire result sets in memory to maintaining only a limited number of rows at a time, reducing peak heap memory usage and preventing OutOfMemory errors.
 - Added new artifact `databricks-jdbc-thin` for thin jar with runtime dependency metadata.
 - Introduce a memory-efficient columnar data access mechanism for JDBC result processing.
+- Added support for using a custom Discovery URL in U2M flows on AWS and GCP.
 
 ### Updated
-- Databricks SDK dependency upgraded to latest version 0.60.0
+- Databricks SDK dependency upgraded to latest version 0.64.0
 - Updated the default value of RowsFetchedPerBlock to 100K from 2M to capture typical cases and balance memory usage.
 
 ### Fixed

development/.release-freeze.json

@@ -1,5 +1,5 @@
 {
   "freeze": true,
   "reason": "Releasing JDBC - 16th Sep",
-  "allow_list": ["jayantsing-db/default-max-rows-per-block", "ResultSetMetadataFix", "PECOBLR-951"]
+  "allow_list": ["samikshya-chand_data/upgradesdk"]
 }

pom.xml

@@ -56,7 +56,7 @@
     <httpclient.version>4.5.14</httpclient.version>
     <commons-configuration.version>2.10.1</commons-configuration.version>
     <commons-io.version>2.14.0</commons-io.version>
-    <databricks-sdk.version>0.60.0</databricks-sdk.version>
+    <databricks-sdk.version>0.64.0</databricks-sdk.version>
     <maven-surefire-plugin.version>3.1.2</maven-surefire-plugin.version>
     <sql-logic-test.version>0.3</sql-logic-test.version>
     <lz4-compression.version>1.8.0</lz4-compression.version>