Support ability to customize storage classes across mas install, instead of using unique RWO and RWX across the pipeline

[andrercm]

This is already supported in ansible-devops, but in cli we just define one RWO and RWX storage class across the pipeline.

This has been a request for enhancement brought by two business partners that are active contributors and users of our automation engine.

[durera]

To what end? What's the use case we have in mind where there's sufficient difference in the storage requirements that one thing that needs RWX and another that also needs RWX would be configured with two different storage classes? Just because we can doesn't always mean we (or our business partners) should, there may be a good reason for supporting this, but I'd like to have that reason clearly defined to justify the extra complexity it brings, which IMO provides minimal value.