Bug: `exclude_*` credentials in DefaultAzureCredential in azureml-mlflow

Apologies if this is posted in the wrong place, I'm happy to re-post if you can point me in the right direction - it's regarding `azureml-mlflow`.

The `azureml-mlflow` plugin currently uses a blank `DefaultAzureCredential()` call to generate credentials to track ML Flow runs. The `DefaultAzureCredential()` actually accepts a number of `exclude_*` arguments to avoid trying to use certain types of credentials.

Not being able to pass those `exclude_*` arguments to the `azureml-mlflow` plugin means that in some situations (experienced whilst on a customer-granted Azure hosted VM) it will try to use the machine's managed identity even when we explicitly do not want to.

Are there any plans to make those options available to us using azureml-mlflow?

先找出 azureml-mlflow 外掛程式建構其 DefaultAzureCredential 的位置，然後檢查可用的 exclude_* 選項。確認呼叫端可以如何提供這些選項，並新增涵蓋範圍以顯示可以排除 managed identity；完成的條件是外掛程式公開所要求的 credential 控制項，同時不破壞現有行為。

由索引模型根據 Issue 內容生成。