Add cmdlets to management Network ACL

[EmmaZhu]

Description

Add Cmdlets to manage NetworkRule for Vnet.

The code logic is same with the before PR #4210, but some name change and output format change as feature team requested.

---

This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

• [Y] I have read the contribution guidelines.
• [Y] If changes were made to any cmdlet, the XML help was regenerated using the platyPSHelp module.
• [Y] If any large changes are made to a service, they are reflected in the respective change log.

General Guidelines

• [Y] Title of the pull request is clear and informative.
• [Y] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
• Y] The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

• [Y ] Pull request includes test coverage for the included changes.
• [Y ] PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

• [Y ] New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
• [Y ] Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

• [Y ] Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
• [Y ] Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
• [ Y] Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

[blueww]

On Demand Test: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1758

[cormacpayne]

@EmmaZhu @blueww I had to stop the on-demand job since there is an issue with the on-demand and sign jobs hanging during help generation. I'll get the fix out, pull it into this PR and kick off another on-demand run.

[cormacpayne]

On-demand: http://azuresdkci.cloudapp.net/job/powershell-demand/1759/

[blueww]

Update the output format of Get/Update-AzureRmStorageAccountNetworkRuleSet (already discuss and agreed with Mark online), On Demand test run again in : http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1763/

[cormacpayne]

@EmmaZhu @blueww please make sure the ```yaml string is on a line by itself (see other parameters in this file as example). This will allow the markdown file to be rendered correctly.

[cormacpayne]

@EmmaZhu @blueww same comment

[cormacpayne]

@EmmaZhu @blueww made two minor comments. Otherwise, LGTM

[blueww]

@cormacpayne
The 2 comments for help has been resolved.
The on-demand test with the fix is in: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/1771/

Thanks!

[markcowl]

In the future, I woudl consider a separate parameter set with string parameters for NetworkRuleId and IPAddressOrRange - this would make this cmdlet parallel with the create cmdlet

Changes have been made as specified