[App Service] Support for ServiceTag, multi-ip and http-headers in Access Restrictions

[madsd]

Description

This PR introduces support for ServiceTags, multi-ip and http-headers in App Service Access Restrictions

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
  • the markdown help files have been regenerated using the commands listed here

[madsd]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[madsd]

/azp run azure-powershell - windows-powershell

[azure-pipelines]

No pipelines are associated with this pull request.

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[madsd]

/azp run azure-powershell - powershell-core

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[madsd]

/azp run azure-powershell - powershell-core

[azure-pipelines]

No pipelines are associated with this pull request.

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[isra-fel]

Looks good

[madsd]

I have tried multiple times to get the powershell core - Test Windows to complete - but it keeps timing out after 180 minutes. Seems to be Sql Tests taking almost two hours to run.

[isra-fel]

I have tried multiple times to get the powershell core - Test Windows to complete - but it keeps timing out after 180 minutes. Seems to be Sql Tests taking almost two hours to run.

Yeah I've been debugging quite a long time but still no luck to locate the root cause 😕
Anyway you can leave the job to me. I'll make sure this PR get merged in the upcoming release.