Upgrade storage client & support Entra identities for storage in more scenarios

[aelij]

Issue describing the changes in this PR

Resolves #3376

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• I have added all required tests (Unit tests, E2E tests)

PR overview:

• Upgrade to the latest Storage client
• Use AzureCliCredential and AzurePowerShellCredential to fetch an access token instead of the code that calls the CLIs
  • Note I intentionally did not use DefaultAzureCredential to preserve the current behavior, as it might require the user to specify a tenant ID under certain conditions
• Support AzureWebJobsStorage__accountName in more scenarios:
  • Linux Consumption - fetches the storage account key using ARG+ARM and uses it to create the required SAS URI
  • Linux Elastic - combined code with Dedicated, as both support run from package
• Remove old unused app.config (.NET Framework relic)

[xanecs]

Hi, I've tried your fork and with a few minor exceptions, it worked perfectly and solved my deployment problem. Thank you!

There are just two small changes I've made to allow working with a Storage Account that has Shared Keys turned off.

[xanecs]

Remove the StorageSharedKeyCredential and use this.Credential instead.
This allows disabling Shared Keys on the storage account altogether.

[xanecs]

Again, to allow disabling Shared Keys on the storage account, return blob.Uri in case managed identity is used.