feat(publish-site-azure.yml): adds workflow to move documentation + PR previews to Azure

[cdransf]

Description

CSS-1217

• Adapts setup steps from existing Netlify workflow
• Changes deploy destination from Netlify to Azure
  • Triggered when a PR is opened, updated and reopened
  • Cleans up environment/deploy when PR is closed
• Programmatically removes excess Azure workflow comments

How and where has this been tested?

Tested and verified using production GitHub workflow environment.

To-do list

• I have read the contribution guidelines.
• I have updated relevant storybook stories and templates.
• I have tested these changes in Windows High Contrast mode.
• If my change impacts other components, I have tested to make sure they don't break.
• If my change impacts documentation, I have updated the documentation accordingly.
• ✨ This pull request is ready to merge. ✨

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1179c61

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

File metrics

Summary

Total size: 1.42 MB^*

🎉 No changes detected in any packages

* Size is the sum of all main files for packages in the library.
* An ASCII character in UTF-8 is 8 bits or 1 byte.

[github-actions]

📚 Branch Preview

PR #3957 has been deployed to Azure Blob Storage: https://spectrumcss.z13.web.core.windows.net/pr-3957/index.html.

[github-actions]

📚 Branch preview

PR #3957 has been deployed to Azure Blob Storage: https://spectrumcss.z13.web.core.windows.net/pr-3957/index.html.

[castastrophe]

If you want to, we can rename these suggested titles and it would match the required workflows for the branch that exist today. Or we can just update branch requirements after this merges.