for Guacamole VMs, the 'Stop' and 'Disable' button semantics are not clear.

Describe the bug
A VM in Guacamole can be disabled with the 'Stop' button from the 'Actions' menu, or with the 'Disable' button, Both appear to do the same thing, from the viewpoint of the TRE interface, in that they show the VM in the same state, and it's no longer possible to connect to it.

However, the 'Disable' button leaves the VM running, as seen in the Azure portal. This is misleading, I would expect that disabling the VM would shut it down and deallocate it.

Similarly, just for fun, if I shut down the VM in the Azure portal, the TRE portal reflects this status when I refresh, but the 'Enable' button doesn't seem to do anything at all. In short, the Enable and Disable buttons seem to serve no purpose for VMs.

Steps to reproduce

1. Create a VM via Guacamole
2. Disable it via the TRE
3. Note that it's still running in the Azure portal.

N.B. it would be nice to at least have meaningful tooltips for the Update/Disable/Enable buttons, that would go some way to avoiding potentially costly mistakes.

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

Deployed Azure TRE components - click the (i) in the UI:
UI Version: 0.5.21
API Version: 0.18.5

Start by reproducing the disable, enable, and Azure Portal scenarios described in the issue, comparing the TRE display with the VM's actual state. Trace the UI actions and their Azure effects, then verify that Stop, Disable, and Enable have distinct, accurate behavior or clearly explain their semantics through tooltips.