Azure bastion should always create the local SSH private key

Currently, azure bastion only creates the private key (~/.ssh/{name}) on first run (or when the jumpbox private key has changed). This means that subsequent engineers have to manually run the command to get the bastion SSH key for use with the proxy.

We could probably use something like https://www.pulumi.com/registry/packages/local/api-docs/file/ to better handle the local file creation. Note that this requires us to add terraform providers though which is non-trivial (but also probably necessary in the long run).

Locate the Azure Bastion command and the existing logic that creates ~/.ssh/{name}; start by tracing when that logic runs and review the proposed Pulumi local file provider and Terraform provider implications. Done means subsequent engineers receive the local Bastion SSH private key without manually rerunning a command.