Sync to 2.31.0 upstream chart repo & add missing volume snapshot resource and CRDs (SC-3707)

[phantasm66]

There are some much needed features in the latest Velero chart 2.31.0 (we are currently running 2.17.2). The main one being the added ability to allow Velero to update existing resources in place, instead of saying they already exist and erroring. This is essential for our Zeebe PV restore DR strategy. The velero backed up PV and PVCs cannot be restored with older version of Velero unless the PVs and PVCs are deleted first.

In addition to the new existingResourcePolicy: update feature, I'm also adding the core kubernetes CRDs that are required for the Velero VolumeSnapshotClass CRD (needed for allowing Velero to backup CSI managed PV (EBS) volumes).

Broken down by commits:

1. sync this forked repo with upstream velero helm chart's 2.31.0 release
2. add velero's VolumeSnapshotClass resource for CSI EBS driver
3. add the missing core Kubernetes CRDs that velero's VolumeSnapshotClass resource requires
   
4. Include the original changes for the fork that were done here: Fork velero chart and make modifications to work with GitOps #1

I added commits 2 and 3 to this forked top level helm chart (instead of putting them in our sub chart in kubernetes-clusters) because the CRDs and VolumeSnapshotClass resource are 100% required for our kubernetes cluster setups (they all run Velero).

Tested in staging1 (live now)

All existing backup schedules, backups, PVs etc.. were all retained and the new Velero appVersion is correct 1.9.0 and the needed CRDs and volume snapshot class stuff was also all created. Tested backup and restore w/ Jon G.. works fine.

I'll have a PR up for the staging1 (and also production1) sub chart changes to use this new chart version shortly. I also already built and pushed this new parent (forked) chart version to AF (hence, I was able to test w/ our sub chart in staging1).

[corymurphy]

What was the original purpose of forking this chart? Did those features get rolled into the official chart yet?

[phantasm66]

What was the original purpose of forking this chart? Did those features get rolled into the official chart yet?

There are a lot of references in newer PRs to those two PRs (now closed) that are in this fork's ezREADME, however for us (and anyone using newer ArgoCD, which uses Helm v3), the fix implemented in vmware-tanzu#171 does not address the underlying issue. See vmware-tanzu#171 (review) for details on why.

It's essentially a Helm lifecycle thing, by design.