Support QoS Priority Configuration via NVMe Connect Command instead of hardcoding it on storage and host

1. IBM Design
Before PFC can work properly, clients must configure the QoS value on both the storage and host sides. However, IBM Storage only supports configuring a single QoS value at the storage level, which limits the flexibility to assign different PFC priorities to individual host connections.

2. NetApp Design
NetApp allows clients to specify the QoS priority directly through the nvme connect command on the host, providing greater flexibility for configuration.

3. Customer Use Case and Limitation
In the TSMC environment, multiple databases and hosts connect to the same storage system. Different databases may require different PFC priorities based on their workload requirements. For example, one database may need PFC priority 3, while another requires priority 5.

With the current IBM design, configuring different PFC priorities for individual connections is not flexible enough to meet this requirement, particularly when the QoS value must be configured and maintained on both the storage and host sides.

4. Feature Request
Please urgent enhance the IBM design to allow clients to specify the QoS/PFC priority directly through the nvme connect command on the host, similar to the NetApp approach. This would enable per-connection priority configuration, simplify management, and better support multi-database environments like TSMC.

Thank you for your consideration.