Optimise Wizard Web App Deployment/testing process

[Gordonby]

The release process for the Wizard web app is a little bit contrived.

The following items have been identified as optimising the release process

• Decouple validation and release of GitHub pages
• No longer build and store the json in the repo. It will purely be a release artifact

In validation

• on pr raise, automatically add a label of full-integration-tests
• run a bicep build to invoke the linter explicitly
• remove fragile test files from repo
• if the PR is draft and label full-integration-tests is not present, don't run the full integration tests
• run actual deployment

In release

• bicep build the compiled json (and remove from the push step)
• calculate the semantic version number (using 2 new labels for release minor and patch ?) Increment just the last patch number tag/release
• create a draft GitHub release (using the gh cli)

[github-actions]

Issue smells stale, no activity for 20 days. Stale Label will be removed if the issue is updated, otherwise closed in a week.