[Storage] Support NFS file share

[blueww]

The added cmdlet has pass review: https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/1488

Description

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.

[github-actions]

‼️ DO NOT MERGE THIS PR ‼️
This PR was labeled "Do Not Merge" because it contains code change that cannot be merged. Please contact the reviewer for more information.

[blueww]

The PR check fail with exception in static analysis BreakingChange.
Any idea how to resolve this?

  There are failed tasks: BreakingChange
  Write-Error: Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object.
     at StaticAnalysis.BreakingChangeAnalyzer.CmdletMetadataHelper.CheckForChangedOutputType(CmdletMetadata oldCmdlet, CmdletMetadata newCmdlet, ReportLogger`1 issueLogger) in D:\a\_work\1\s\tools\StaticAnalysis\BreakingChangeAnalyzer\CmdletMetadataHelper.cs:line 231
     at StaticAnalysis.BreakingChangeAnalyzer.CmdletMetadataHelper.CompareCmdletMetadata(List`1 oldCmdlets, List`1 newCmdlets, ReportLogger`1 issueLogger) in D:\a\_work\1\s\tools\StaticAnalysis\BreakingChangeAnalyzer\CmdletMetadataHelper.cs:line 105
     at StaticAnalysis.BreakingChangeAnalyzer.BreakingChangeAnalyzer.RunBreakingChangeChecks(ModuleMetadata oldModuleMetadata, ModuleMetadata newModuleMetadata, ReportLogger`1 issueLogger) in D:\a\_work\1\s\tools\StaticAnalysis\BreakingChangeAnalyzer\BreakingChangeAnalyzer.cs:line 239
     at StaticAnalysis.BreakingChangeAnalyzer.BreakingChangeAnalyzer.Analyze(IEnumerable`1 cmdletProbingDirs, Func`2 directoryFilter, Func`2 cmdletFilter, IEnumerable`1 modulesToAnalyze) in D:\a\_work\1\s\tools\StaticAnalysis\BreakingChangeAnalyzer\BreakingChangeAnalyzer.cs:line 196
     at StaticAnalysis.BreakingChangeAnalyzer.BreakingChangeAnalyzer.Analyze(IEnumerable`1 cmdletProbingDirs, IEnumerable`1 modulesToAnalyze) in D:\a\_work\1\s\tools\StaticAnalysis\BreakingChangeAnalyzer\BreakingChangeAnalyzer.cs:line 66
     at StaticAnalysis.Program.Main(String[] args) in D:\a\_work\1\s\tools\StaticAnalysis\Program.cs:line 189

[notyashhh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[notyashhh]

/azp run

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.