Update publish-AzWebApp to support pull based deployments.

[dannysongg]

Description

Add support for pull based deployments from a URL with MSI authentication in Publish-AzWebApp. This change adds 2 parameters to enable this feature: ArchiveURL and -PullIdentity.

Notable Changes:

• Add ArchiveURL parameter
• Add PullIdentity parameter
• ArchivePath is no longer a required parameter. ArchivePath OR ArchiveURL must be provided. If both are provided, ArchivePath will be ignored

-PullIdentity Usage:

• null: MSI will not be used. This matches the existing behavior (SAS or public access)
• system: Authenticates using system assigned identity
• {client-Id}: Authenticates using provided user assigned identity

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.