Unable to acquire Additional Disks/volume for Proxmox VMs – Primary Storage Not Available in CloudStack 4.22

### problem

We have deployed the latest CloudStack version 4.22 in our test environment and are using Proxmox as the hypervisor. Earlier, we faced an issue where CloudStack always selected local-lvm on Proxmox instead of shared storage. That issue was resolved based on this previous discussion:
https://github.com/apache/cloudstack/issues/12163

Now, after that fix, VMs are successfully created on the shared storage. However, we are facing a new problem:

Issue:
When we try to acquire an additional disk to a VM, CloudStack does not show any usable primary storage options for the Proxmox cluster.

Details:

When adding Primary Storage:
If we select Scope: Cluster, the only storage option available is NFS
If we select Scope: Zone and Hypervisor: Any, only NFS is shown.
If we select Scope: Host or Scope: Cluster and choose Proxmox, CloudStack incorrectly shows XCP-ng hosts instead of Proxmox hosts.

Impact:
Because no primary storage can be properly added for Proxmox clusters, we are unable to acquire additional data disks for VMs.

### versions

CloudStack: 4.22
Hypervisor: Proxmox VE 8.x
Storage Type: (Shared Storage)
Nodes in cluster: 2
Using Proxmox with CloudStack extension

### The steps to reproduce the bug

### What to do about it?

_No response_

Start by reproducing the issue with CloudStack 4.22, Proxmox VE 8.x, shared storage, and a two-node cluster; the issue does not provide a reproduction procedure or name files or tests. Compare the storage options for Proxmox cluster, host, and zone scopes, and consider the issue done when usable Proxmox primary storage is shown and an additional VM disk can be acquired.

Written by the indexing model from the issue text.