[Bug] ResourceQuotaExceeded error is not reported on the GUI when starting persistent VMs

[frisso]

The intended behaviour, as shown below, is displaying the error when a user is trying to start a new instance that would result in exceeding the resource quota assigned to them:

When a user is reaching their limits in terms of assigned resources, new instances are never started, but no error is given in case of persistent VirtualMachine environment templates. So, the user is waiting for the instance to start (which never happens) without understanding the situation.
This is an example of a user very close to its limits:

And this is what happens to the VM that never starts:

Note: The reason behind is that a VM instance retrieves the ResourceQuotaExceeded phase from its VirtualMachineInstance (VMI) object, which is created directly by the Instance Operator in case of non-persistent VM templates. As for persistent ones, the Instance Operator first creates a VirtualMachine object, which in turn should create a VMI but never does to not exceed the resource quota. This bug does not concern container and standalone environments, which, while being persistent, are instantiated differently.