Add prefix to naming of PV

[mschwehl]

Is your feature request related to a problem?/Why is this needed
In the current state, dynamically provisioned PersistentVolumes (PVs) are named with generic, opaque names like:
pvc-9e1fafe5-ec2b-4c4e-8062-0fac5e8a53xx.
This naming makes it difficult to identify what data is stored in the volume, especially in disaster recovery (DR) scenarios or when managing a large number of volumes. As a result, administrators must spend extra effort correlating volumes to applications, increasing risk and downtime during recovery.

Describe the solution you'd like in detail

Ideally, the generated PV name should allow inclusion of a human-readable prefix that reflects the application's purpose. For example:

pvc-jira-data-9e1fafe5-ec2b-4c4e-8062-0fac5e8a53xx make the content inside clear. in that case some jira data

This would immediately clarify that the volume contains Jira-related data, and simplify DR operations, backups, and audits.

Describe alternatives you've considered
https://jbn1233.medium.com/kubernetes-csi-csi-driver-nfs-with-subdir-132d3e04e424 shows you can use subdir but thats not self explanatory

Additional context
other drivers points us to a solution
kubernetes-csi/external-provisioner#86

kind: StorageClass
parameters:
  volumePrefix: "jira-data"

Downside is we have to create a storage-class for each app but have better naming. Much better will be if you can specify via PVC