Adding PowerShell Deployment Option to the Helper

[fireblade95402]

PR Summary

Added deployment option for PowerShell. Decided to to NOT change the az cli commands to PowerShell and only really change the postdeploy.sh script to postdeploy.ps1. I needed to change syntax in the helper and the release action to add in the new script, plus logic the handle old releases where the postdeplo.ps1 isn't available.

PR Checklist

• PR has a meaningful title
• Summarized changes
• This PR is ready to merge and is not Work in Progress
• Link to a filed issue
• Screenshot of UI changes (if PR includes UI changes)
  

[fireblade95402]

Need to check with the team on any functionality that might have been missed

[Gordonby]

The tab is disabled for me.
Is that expected?

[fireblade95402]

@Gordonby It has logic to disable the PowerShell tab if the postdeploy.ps1 isn't in the release. So need a release to test it out.

[github-actions]

PR smells stale, no activity for 30 days. Stale Label will be removed if the PR is updated, otherwise closed in a month.

[khowling]

Mark, I've setup a review meeting to discuss, things I want to check is to ensure it works with private clusters, and local testing. And to ensure we have some test coverage in the actions.

[Gordonby]

I'm getting an error when running this command

az deployment group create -g gordons  --template-file ./bicep/main.bicep --parameters `
resourceName=az-k8s-krcu `
SystemPoolType=Standard `
availabilityZones='["1","2\",\"3"]'

InvalidAvailabilityZoneFormat

The specified Availability Zones [1 2\\\",\\\"3] are invalid and should be in numeric format.

    "error": {
        "code": "InvalidAvailabilityZoneFormat",
        "target": "agentPoolProfile.availabilityZone",
        "message": "The specified Availability Zones [1 2\",\"3] are invalid and should be in numeric format."
    }

[Gordonby]

lgtm