Fix issue with Network help

[cormacpayne]

Description

• Fixed issue with markdown for Add/Get/New/Remove-AzureRmExpressRouteCircuitAuthorization where INPUTS and OUTPUTS sections were formatted incorrectly
• Fixed issue with markdown for Get-AzureRmVirtualNetworkGatewayBCPPeerStatus and Get-AzureRmVirtualNetworkGatewayLearnedRoute where examples contained two code blocks that needed to be merged into one
• Regenerated the XML help file to include these changes

---

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.

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

General Guidelines

• Title of the pull request is clear and informative.
• 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.
• The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

• Pull request includes test coverage for the included changes.
• 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

• 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.
• Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

• Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
• 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.
• Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

[cormacpayne]

@lamchester @sdwheeler please take a look at this PR

It looks like when we merged Chester's PR (#3614) it reverted some of the changes that Sean made to the Network help, so I went ahead and updated the markdown for Add/Get/New/Remove-AzureRmExpressRouteCircuitAuthorization based on what previously existed.

There was also an issue with the formatting of examples in the markdown files that Chester added for the new cmdlets in his PR, so I just moved a couple of things around to stop platyPS from throwing when trying to generate the XML help from the markdown files.

Please let me know if anything jumps out.

[anavinahar]

Update on this? @cormacpayne @lamchester @sdwheeler This is blocking changes that need to be made to PS help.

[sdwheeler]

@cormacpayne @lamchester @anavinahar It looks like the content for a different cmdlet was put in these files in Chester's PR. For example, the content for Add-AzureRmApplicationGatewayUrlPathMapConfig was put into Add-AzureRmExpressRouteCircuitAuthorization.md. The corrections in this PR look good to me.