Add option to have runner PVCs created with workflow name in the PVC name

What would you like added?

A clear and concise description of what you want to happen.

Note: Feature requests to integrate vendor specific cloud tools (e.g. awscli, gcloud-sdk, azure-cli) will likely be rejected as the Runner image aims to be vendor agnostic.

An option to add a PVC to runners with the workflow id in the name. This would allow a volume to be created that could be shared accross multiple jobs. This would have to be set as ReadWriteMany in the case of parallel jobs.

Why is this needed?

A clear and concise description of any alternative solutions or features you've considered.

This could solve a bunch of issues in regard to dependency caching and shared workspaces accross jobs.

Additional context

Add any other context or screenshots about the feature request here.

Start by tracing how runner PVCs are currently created in the controller and how workflow identifiers reach that path. Review the Kubernetes PVC settings needed for shared volumes, then define the option's naming and access-mode behavior. Done means an opt-in PVC named with the workflow identifier can be shared by parallel jobs.