Use AzCLI instead of client secret creds

[wonwuakpa-msft]

Description

• Changes:

  • Removed the requirement for the client secret env variable NEW_E2E_STATIC_CLIENT_SECRET.
  • Replaced usages to have AzCLI instead.

• Feature / Bug Fix: (Brief description of the feature or issue being addressed)

  • Migrated from using client secret credentials to AzCLI for static storage account tests in the e2e framework.

• Related Links:

  • Issues

Type of Change

• Bug fix
• New feature
• Documentation update required
• Code quality improvement
• Other (describe):

How Has This Been Tested?

Thank you for your contribution to AzCopy!

[adreed-msft]

Nitpicks/suggestions, nothing ship-sinking. Looks good!

[adreed-msft]

nit: this could be done as an either/or setup

weigh this with a grain of salt, most of the team will probably do inherited auth

[adreed-msft]

on a similar note, could it be set up to allow AzCLI or AzPwsh inheritance? Some people on the team use one or the other, not usually both

[gapra-msft]

Let's add the option of Pwsh as a separate PR just to keep things simple now. @adreed-msft could you create an item for that under AzCopy as a library?

[gapra-msft]

lgtm. If adding Pwsh as an option is easy enough, feel free to add it in this PR as an alternative. Otherwise, please work with Adele to make sure its tracked for a future add.