I think it would be nice to reevaluate default PVC strategy.

Before `perWorkspace` strategy was introduced, we were stuck with `common` as default PVC strategy, because `unique` created lots of PVCs. This was mitigated by introducing `perWorkspace` strategy in upstream Che, which I think is best solution for now.

I'm raising this mainly because of deployment of CRW to OSD. As I understood, OSD is not backed by storage with RWX support and `common` strategy is not a good fit for this.

And for other deployments of CRW I think this strategy brings best of both approaches