feat(vm-storage-labeling): add storage volume labeling role

[stevefulme1]

Summary

• Adds vm_storage_labeling role and playbook to apply labels, annotations, and descriptive names to PersistentVolumeClaims (PVCs) and DataVolumes at the OCP level
• Supports targeting volumes by name or label selectors for bulk operations
• If a PVC is owned by a DataVolume, labels/annotations are applied to both resources
• Follows existing collection patterns for variable naming, validation, and k8s JSON patch operations

Moved from

Originally submitted as redhat-cop/openshift_virtualization_migration#15 — relocated here as this is day 2 ops functionality (managing storage on existing VMs), not migration logic.

FQCN updated from infra.openshift_virtualization_migration to infra.openshift_virtualization_ops.

Test plan

• Verify yamllint passes
• Verify ansible-lint --offline passes production profile
• Integration test: apply labels to PVCs by name in a test namespace
• Integration test: apply labels to PVCs by label selector
• Integration test: verify DataVolume-owned PVCs also patch the DataVolume
• Verify idempotency — re-running with same labels produces no changes

🤖 Generated with Claude Code

[sabre1041]

@stevefulme1 This looks good. Only comment is related to my prior comment whether there was a requirement to scope to either a namespace or by labels. In the vm_collect role, a namespace is only required when names are specified. Not a blocking item. However, it provides alignment to other capabilities within the collection

In addition, would you be able to review the conflicts in the test-requirements.txt file?