Creation of Arbitrarily Named PVCs

[dan-fernandes]

Blueapi currently creates a PVC if .Values.initContainer.persistentVolume.enabled is true, and .Values.initContainer.persistentVolume.existingClaimName does not have a value.

This means that while Blueapi can connect to arbitrarily named PVCs, it can only create one PVC per version.

There is a use case for beamlines needing a clean PVC, without having changed versions and whilst retaining a roll-back option.

Acceptance Criteria

• Blueapi can create and connect to arbitrary PVCs

[dan-fernandes]

This is a really small change. but could be a major (api breaking) helm chart change.