Describe the bug
We are encountering a situation where requesting VM changes (e.g. Stop/Start) seems to be working but the API never seems to pick up the resource status changing and the UI just spins on the "awaiting action" status. These workspaces/VMs were working normally earlier today and there has not been any code changes since.

Steps to reproduce

1. Select a VM in the TRE UI with either the Stopped or Started state.
2. Start (or Stop) the VM via the TRE UI
3. The Operations page will show "Status: awaiting_action" indefinitely.
4. Checking the VM's state via the Azure Portal shows it in the Running (or Stopped) state.

Azure TRE release version (e.g. v0.14.0 or main):
v0.21.0

Deployed Azure TRE components - click the (i) in the UI:
tre-service-guacamole (0.12.9)
tre-service-databricks (1.0.10)
tre-service-azureml (0.9.2)