…01 to version 2020-05-01

…ualApplianceSites child resources (#9357)

* Adds base for updating Microsoft.Network from version stable/2020-03-01 to version 2020-05-01

* Updates readme

* Updates API version in new specs and examples

* Final changes

* Fix formatting issues

* Fix merge and formatting issues

* Fix formatiing

* Ipconfig properties

* Fix build errors

* Lint check

* Fix semantics errors

* Address review comments

* Fix prettier and nextLink checks

* Fix dots

* Address errors

* Fix Ipconfig version

Co-authored-by: dexiang-ms <64503627+dexiang-ms@users.noreply.github.com>

* Adding DnsProxySettings Support in Firewall Policy

dnsServers, dnsEnableProxy, dnsRequireProxyForNetworkRules are added as subproperties.

* spell check

* Removing DNS as prefix on sub properties.

* Syntax error.

* DnsProxySettings to DNSSettings

* Fixing proxy settings name.

Co-authored-by: Ishani Gupta <isgu@microsoft.com>

* fix network

* duplicated publicipprefix

* fixed example in 2018-01-01

* final updates

* missing examples

(cherry picked from commit 42d9639)

* Added new properties to ConnectivityHop

* Fixed spelling

* added x-ms-client-flatten to HopLink.properties.properties

#9356)

* Rename Firewall Policy child resource RuleGroup to RuleCollectionGroup

* rebase with ti whitelist

* rebase with ti whitelist

* rebase with ti whitelist

* prettier run

* making nat rule into a collection

* prettier run

* multi pip for firewall in hub swagger change

* resolving issues

1. Exposed direct PUT/DELETE APIs for hubvnet connections. This is the
   API expected to be used in the future by all consumers (direct rest
   api calls, powershell, portal, azure cli). This avoids needing a put
   on the virtual hub every time a hubvnet connection is to be
   added/changed.
2. Deprecate specifying hubvnet connection in virtualHub PUT. This is to
   avoid having multiple APIs to do the same thing. Also having this API
   introduces other complexities and breaks some scenarios.
3. Deprecate allowHubToRemoteVnetTransit and
   allowRemoteVnetToUseHubVnetGateways flags in hubvnet connection.
   These flags are maintained internally in the implementation and
   shouldn't be exposed to the user. For now, just mark it as such. Will
   be removed in later release.

Co-authored-by: Shyam Dharmarajan <shdharma@microsoft.com>

* v1

* making boolean as nullable

Co-authored-by: Ishani Gupta <isgu@microsoft.com>

* Add Routing State and expose Effective Routes Api

* updated opId name and added examples

* prettier fix done

* rename variable to prevent conflict

* Updating VpnGateway examples

* prettier

Co-authored-by: Khushboo Baheti <khbaheti@microsoft.com>

* Application Gateway Private Link Support

* Fix comments

* Fix comments for including example