Fix random windows CI failure

[guotuofeng]

Describe your changes

1. According to https://learn.microsoft.com/en-us/azure/devops/pipelines/release/troubleshoot-workload-identity?view=azure-devops#error-messages, the AzureCLI task not work well with az account get-access-token since our CI pipelines will fail on Windows_CI_Test_Examples resnet_ptq_cpu. the error message is like:

• AzureCliCredential: ERROR: AADSTS700024: Client assertion is not within its valid time range. Current time: 2024-04-08T03:00:10.8235174Z, assertion valid from 2024-04-08T02:29:38.0000000Z, expiry time of assertion 2024-04-08T02:39:38.0000000Z. Review the documentation at https://docs.microsoft.com/azure/active-directory/develop/active-directory-certificate-credentials . Trace ID: 9e51fd4c-88a8-4c52-b862-5daaf31d2400 Correlation ID: 55cbfee9-c8b7-4627-91ba-36cfcaa58ae8 Timestamp: 2024-04-08 03:00:10Z
  Interactive authentication is needed. Please run:
  az login

  From the error message, it seems the idToken is about 10 minutes. From ERROR: AADSTS700024: Client assertion is not within its valid time range Azure/login#180 (comment) and https://devblogs.microsoft.com/devops/public-preview-of-workload-identity-federation-for-azure-pipelines/#comment-4001, it might/might not be the azure service connection issue.

• How to fix/work around: in this PR, I adjust the execution order of aml_system and local_system to make sure the idToken is not expired since of the 10 minutes timeout.

  Let's wait and rerun to check whether the CI failure is fixed or not.

2. In Olive, we need only change the azure logging level if the user doesn't specify them.

Checklist before requesting a review

• Add unit tests for this change.
• Make sure all tests can pass.
• Update documents if necessary.
• Lint and apply fixes to your code by running lintrunner -a
• Is this a user-facing change? If yes, give a description of this change to be included in the release notes.
• Is this PR including examples changes? If yes, please remember to update example documentation in a follow-up PR.

(Optional) Issue link

[guotuofeng]

#1060 fix the issue by managed identity.