feat: automation to deploy IaC

[kevholmes]

I need to add some automation here. Right off the top of my head I'm thinking it would be best to write an Actions workflow that has a few parts:

CI/CD

1. Lint Go code / Pulumi code with SA tools in PRs
2. Ensure code builds in PRs
3. GitOps approach with PRs planning and deploying to dev env. Release-please PRs will plan/deploy to staging env before they are merged. Official/full Releases generated in GH w/ semantic versions will be automatically deployed to production when the Release creation event is generated in GH or through manual workflow_dispatch with a provided tag/semver.

For Authentication/Authorization to Azure I'll need to set up a Service Principal w/ scoped access to the areas where this IaC touches. That will be outside the scope of this repo but I can include a manual az cli command that will accomplish that task within this repo's documentation so we have a full A -> Z setup routine that's repeatable.

[kevholmes]

Items 1 and 2 have been resolved here #23.

[kevholmes]

I have CI checks for pulumi preview per each environment now added to all PRs: #83.