chore: add operations scripts for maintaining infrastructure

[awentzel]

Description

This merges CLI work for managing the Azure infrastructure. These scripts perform operations for creating new services, destroying old services, and updating existing services. This is beta and mostly usable with some features yet to be implemented which are documented in comments and with GH issues.

This begins a FAST CLI extending the Azure CLI simplified maintainability with consistency, speed, and reliability.

Motivation & context

To provide an equal ability for all collaborators to perform common service needs. For example, perform release deployments of websites.

Issue type checklist

• Chore: A change that does not impact distributed packages.
• Bug fix: A change that fixes an issue, link to the issue above.
• New feature: A change that adds functionality.

Is this a breaking change?

• This change causes current functionality to break.

Adding or modifying component(s) in @microsoft/fast-components checklist

• I have added a new component
• I have modified an existing component
• I have updated the definition file
• I have updated the configuration file

Process & policy checklist

• I have added tests for my changes.
• I have tested my changes.
• I have updated the project documentation to reflect my changes.
• I have read the CONTRIBUTING documentation and followed the standards for this project.

[EisenbergEffect]

I can't comment much on the scripts themselves. I haven't written bash scripts anywhere that complexity ;) Glad to see the documentation and get this in. Just want to also confirm that there's nothing in here that could be a security concern in terms of content, config, etc.

[nicholasrice]

@awentzel please add the appropriate feat, fix, or chore flag to the title of this PR.

[marjonlynch]

I'm assuming this is a multi-stage approach, I was able to get the scripts running and after selecting westus got a permissions error which was expected as I don't apparently have permissions for that.