feat: add workload panels in workload dashboard

[rahulguptajss]

This PR changes the workload templates, specifically the workload.yaml and workload_volume.yaml templates, as well as workload_detail.yaml and workload_detail_volume.yaml. For the purpose of this discussion, we will focus on the workload.yaml and workload_volume.yaml templates, although the same applies to workload_detail.yaml and workload_detail_volume.yaml.

Currently, there are three different workload classes: user_defined, system_defined, and autovolume. However, we discovered an issue in the templates where the user_defined workloads were being collected twice, once in workload.yaml and again in workload_volume.yaml. To address this problem, we have implemented the following solutions:

Modification of workload_volume.yaml: This template will now only collect autovolume workloads, removing the collection of user_defined workloads. The workload.yaml template will be responsible for collecting both user_defined and system_defined workloads. If you prefer the previous behavior and want to collect user_defined workloads in workload_volume.yaml, you can adjust the workload_class parameter in the workload templates according to your needs.

Update of the 'object' field in workload_volume.yaml: We have aligned the 'object' field in workload_volume.yaml with the workload.yaml template, changing it to 'qos'. This change simplifies the process of querying workloads. However, it is important to note that this modification may break backward compatibility. If you are affected by this change, you can easily make the necessary adjustment by changing the 'object' field in your workload_volume.yaml template.

[rahulguptajss]

Updated PR as per https://github.com/NetApp/harvest-private/discussions/142

[rahulguptajss]

Ready for review

[cgrinds]

Nice, these changes look good and remove special cases.

Please add as a comment, in this pull request, the high-level description we wordsmithed in email.