feat: (IAC-770) Create new storage class for crunchy v5 PVCs

[dhoucgitter]

Changes

• Create the pg-storage storage class with reclaimPolicy: retain during the baseline install task
• By default, use the pg-storage storage class for internal postgres database server instances.
• Once a set of postgres_servers variable map storage variables have been applied to a cluster during a deployment, the storage class and access modes for those servers can not be updated with a DAC deployment to the same cluster without uninstalling Viya.
• Switch from using the community.kubernetes ansible collection modules to the kubernetes.core ansible collection modules, update Dependencies.md and requirements.yaml

Tests

Development testing to include OOTB 2022.10 executions of DAC to generate site-config/vdm content using DEPLOY:false. Once DEPLOY:true has deployed Viya to the cluster, verify that no updates to v5 crunchy storage class or access mode for either default or cds-postgres instances is allowed along with the output of an ansible message providing that notice to the DAC user. See internal ticket for additional test details including external postgres db, 2022.09 stable order and that the new storage class works properly when "ha" storage_type is configured for each cloud environment.

[dhoucgitter]

Removed collection of v4 PVC attribute info since it will not be used. Update to behavior in roles/vdm/tasks/postgres/postgres-instance.yaml lines 125-129. DAC will exit with "A manual update from crunchy v4 to v5 is required..." if an order with internal v5 crunchy configured is deployed to a cluster where internal v4 crunchy is already present.

[dhoucgitter]

@thpang I've posted updates in response to your review comments, ready for re-review