Fixed error message when creating OAuth based Storage context without first login with Connect-AzAccount

[blueww]

Description

To fix the error message in #26802

Before the fix, it look there's namespace conflict, so the error will be
"Could not find the resource "Microsoft.WindowsAzure.Commands.Storage.Resources.resources" among the
resources "Microsoft.WindowsAzure.Commands.Storage.Common.Resources.resources" embedded in the
assembly "Microsoft.Azure.PowerShell.Storage.Common", nor among the resources in any satellite
assemblies for the specified culture. Perhaps the resources were embedded with an incorrect name."

After fix, the error will be as following ,which will remind user to logon with Connect-AzAccount.

PS C:\> New-AzStorageContext -StorageAccountName here
New-AzStorageContext : Context cannot be null.  Please log in using Connect-AzAccount.
At line:1 char:1
+ New-AzStorageContext -StorageAccountName here
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [New-AzStorageContext], InvalidOperationException
    + FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.Storage.Common.Cmdlet.NewAzureStorageContext

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • For autorest-based development mode, include the changelog in the PR description.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.