fix: exclude node/svm vols and include data svms

[Hardikl]

Naming conventions
volume

• svm_root volume name: xxx_root
• node_root volume name: vol0

SVM

• system_svm: cluster
• node_svm: node name
• admin_svm: cluster name

Before applying on template level filter

Volume:
svm_root: 16

node_root:2

total volume:527

SVM:
data svm:17

node,system,admin svm: 4

total svm: 21

After applying the template level filter
Volume:
total volume: 509

SVM:
total svm: 17

[Hardikl]

For REST,

• Volume public api provide all volumes but node, We only need to exclude root svm vols in template.
• SVM private api provide all svms but system, We only need to include data svms in template.

[rahulguptajss]

I think we should export root vols/svm where applicable and only hide them from dashboards?

[Hardikl]

I think we should export root vols/svm where applicable and only hide them from dashboards?

Yes, We should.
The thought process behind this template filter is, If customer want to exclude/include root objs, they can do via template change which would be easier than query changes in dashboard.

[Hardikl]

[cgrinds]

Nice job @Hardikl