add more authentication method for Azure databricks connector copy data and copy job activity

Please add support for additional authentication methods for the Azure Databricks connector in Fabric/Data Factory Copy Data and Copy Job activities. Current documentation shows that Copy supports Personal Access Token authentication, whereas other experiences such as Dataflow Gen2 support additional authentication methods including Microsoft Entra ID. 

PAT-only authentication is not sufficient for enterprise production scenarios. PATs introduce challenges around security governance, token rotation, ownership, expiry, and operational support. Databricks also recommends OAuth where possible instead of PATs because OAuth provides stronger security. 

In our current Copy Data / Copy Job implementation, we are only able to connect to serverless Databricks SQL/warehouse-style endpoints, and we are not able to use the other Databricks cluster types required for our workloads. This limits flexibility for existing Databricks architectures where teams need to connect to specific non-serverless or interactive compute resources.

Please consider adding support for enterprise authentication options such as:

• Microsoft Entra ID authentication
• Service principal authentication
• System-assigned managed identity
• User-assigned managed identity

This would reduce dependency on PATs, improve security and governance, simplify credential lifecycle management, and provide more flexibility when connecting Fabric/Data Factory Copy activities to Azure Databricks compute.