Improvement request: Allow normal users to select pod or cluster while deploying an instance

##### ISSUE TYPE
* Bug Report

##### COMPONENT NAME
~~~
UI
~~~

##### CLOUDSTACK VERSION
~~~
4.19.1.2
~~~

##### CONFIGURATION
We have 2 clusters called CL01 and CL02. Both of these clusters are dedicated to Account A.
Account A has a role of "User".

##### OS / ENVIRONMENT
Red Hat Enterprise Linux 9.0 using KVM

##### SUMMARY
User accounts in account A have access to 2 different clusters called CL01 and CL02 which are dedicated to account A.
If a user creates a new instance through the UI, the UI doesn't give the user a choice on which cluster they want their instance created. The UI does this selection for them.

If the user creates the instance via the API (ansible script), they are able to choose the cluster and the instance gets deployed.
This tells me that the user (role) does not limit the user in choosing the cluster on which the new instance should land.

If a Root Admin creates a new instance via the UI, they however are able to choose the POD, cluster and even host so the functionality is there in the UI. It's just not given to someone with a "User" role.

##### STEPS TO REPRODUCE
Create a new account called A and assign it the "User" role.
Create a cluster and dedicate this cluster to account A.
Create a second cluster and dedicate this cluster to account A.
As a user from account A, login to the UI and create a new instance.
After selecting the zone in which the new instance should be created, try to select the pod, cluster or host. These options will not be given.

Perform the same steps but now as a Root Admin user and you will be given the choice of pod, cluster and/or host upon creation of a new instance.

##### EXPECTED RESULTS

~~~
After logging in with the role "User", I was expecting to be able to select a cluster on which I could deploy my new instance.
~~~

##### ACTUAL RESULTS

~~~
While logged in as someone with the role "User", I'm not given the choice of selecting the pod, cluster or host upon which my new instance should land.
~~~

Inizia dal flusso di distribuzione delle istanze della CloudStack UI dopo la selezione della zona e confronta i percorsi di User e Root Admin; il report identifica inoltre il percorso di distribuzione tramite API come confronto funzionante. Il lavoro è considerato completato quando un User in un account con più cluster dedicati può selezionare il pod, cluster o host consentito e distribuire correttamente un'istanza.

Scritto dal modello di indicizzazione a partire dal testo della issue.