Virtual Machines Automation from Hypervisors using Qemu-Agent on KVM

##### ISSUE TYPE
* Feature Idea

##### COMPONENT NAME
Categorize the issue, API, KVM, HYP, UI

##### CLOUDSTACK VERSION
Coming versions

##### SUMMARY
Many of us are using Cloudstack to provide public and private cloud services for our internal teams and clients, so normally we don't handle passwords or ssh key password to access the vm's operating system to orchestrate applications lifecycle. So my proposal is that just like user-data works for the first boot we can register actions or commands that we can apply to client's vm using qemu-agent capabilities in KVM so we leverage services like:

- DBaaS
- Managed Applications
- Improvements on CSK

##### STEPS TO REPRODUCE

Cloudstack access the hyp where the vm resides and applies commands like:

virsh qemu-agent-command "$VM_NAME" "$COMMAND_JSON"

Start by mapping how CloudStack reaches KVM hypervisors and where API, UI, and hypervisor actions are defined. Read the qemu-agent-command example and clarify the supported command lifecycle, permissions, and failure handling. Done should include an agreed feature scope and implementation path for applying QEMU-agent actions to guest virtual machines.

Written by the indexing model from the issue text.