Remove custom provider as sdk is now fixed (#1148)

## Description
- The custom azure u2m was a pain because we had to make the sdk flow
for aws inline with the custom flow : this is not possible. Now that sdk
has fixed their flows, we should start using it for azure too.

## Testing
- Tested it manually using Azure U2M

Author: samikshya-db

NEXT_CHANGELOG.md

@@ -15,7 +15,7 @@
 - Removes dangerous global timezone modification that caused race conditions.
 - Fixed `Statement.getLargeUpdateCount()` to return -1 instead of throwing Exception when there were no more results or result is not an update count.
 - CVE-2025-66566. Updated lz4-java dependency to 1.10.1.
-- Fix `INVALID_IDENTIFIER` error when using catalog/schema/table names for SQL Exec API with hyphens or special characters in metadata operations (`getSchemas()`, `getTables()`, `getColumns()`, etc.) and connection methods (`setCatalog()`, `setSchema()`). Per Databricks identifier rules, special characters are now properly enclosed in backticks. 
-
+- Fix `INVALID_IDENTIFIER` error when using catalog/schema/table names for SQL Exec API with hyphens or special characters in metadata operations (`getSchemas()`, `getTables()`, `getColumns()`, etc.) and connection methods (`setCatalog()`, `setSchema()`). Per Databricks identifier rules, special characters are now properly enclosed in backticks.
+- Fix Auth_Scope handling inconsistency in Azure U2M OAuth.
 ---
 *Note: When making changes, please add your change under the appropriate section with a brief description.*

src/main/java/com/databricks/jdbc/api/impl/DatabricksConnectionContext.java

@@ -333,13 +333,9 @@ public List<String> getOAuthScopesForU2M() throws DatabricksParsingException {
     if (getParameter(AUTH_SCOPE) != null) {
       return Collections.singletonList(getAuthScope());
     }
-    if (getCloud() == Cloud.AWS || getCloud() == Cloud.GCP) {
-      return Arrays.asList(
-          DatabricksJdbcConstants.SQL_SCOPE, DatabricksJdbcConstants.OFFLINE_ACCESS_SCOPE);
-    } else {
-      // Default scope is already being set for Azure in databricks-sdk.
-      return null;
-    }
+    // Use uniform default scopes for all clouds: sql and offline_access
+    return Arrays.asList(
+        DatabricksJdbcConstants.SQL_SCOPE, DatabricksJdbcConstants.OFFLINE_ACCESS_SCOPE);
   }
 
   @Override