[Feature] Allow for sourcePVC wildcard for StatefulSets/VolumeClaimTemplates

[PrivatePuffin]

Describe the feature you'd like to have.
StatefullSets using VolumeClaimTemplates, or operators creating VCT-like structures, use a standard format of VCTNAME-NUMBER.
By giving us the option to use a wildcard * in the SourcePVC, we could ensure appropiate objects for all VCT PVCs are created.

Downside of which, is that we also need to deal with the requirement of having multiple secrets that currently exists.

What is the value to the end user? (why is it a priority?)

How will we know we have a good solution? (acceptance criteria)

Additional context

[tesshuflower]

At some point we may be trying to implement support for volume group snapshots, which would then work by taking in a label selector to pick PVCs. I think it would make sense to use this approach rather than wildcards as right now a single replicationsource only works with 1 pvc. See volume group enhancement: #1116

[PrivatePuffin]

At some point we may be trying to implement support for volume group snapshots, which would then work by taking in a label selector to pick PVCs. I think it would make sense to use this approach rather than wildcards as right now a single replicationsource only works with 1 pvc. See volume group enhancement: #1116

Agreed!