ci: introduce CI workflow to verify the CRD folder

[tungbq]

Special notes for your reviewer:

Close #480

Introduce CI workflow to verify the CRD folder, this will do following:

• Set up Github Action environment: checkout code, setup kind, velero
• Use velero and kubectl command to generate 2 YAML manifest files
• Use diff command to check if these files are in synced or not
• Archive the diff workspace for later debugging

This was tested on my forked repo:

• case diff found: https://github.com/tungbq/helm-charts-velero/actions/runs/5751960913/job/15591857978
• case no diff found: https://github.com/tungbq/helm-charts-velero/actions/runs/5751904132/job/15591689104

The workflow also collects the artifact YAML manifest files and the diff results:

• For example: https://github.com/tungbq/helm-charts-velero/suites/14794943841/artifacts/841831563
• 

Currently I set the trigger event to run on workflow_dispatch only. Let me know if we need to cover other trigger events based.

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• DCO signed
• Chart Version bumped
• Variables are documented in the values.yaml or README.md
• Title of the PR starts with chart name (e.g. [velero])

[jenting]

Amazing work @tungbq 🤩

[jenting]

@tungbq
CI failed. Could you plz check it?

[tungbq]

@tungbq CI failed. Could you plz check it?

The difference detected in the CI job due to this YAML block:

   status:
     acceptedNames:
       kind: ""
       plural: ""
     conditions: []
     storedVersions: []

These come from the final block of each crds YAML, e.g: https://github.com/vmware-tanzu/helm-charts/blob/main/charts/velero/crds/backuprepositories.yaml#L101-L106

I don't know the root cause for it now. Much appreciated if I could get some help here.
@jenting do you have any advice how to adjust or where could we correct it?

[jenting]

@tungbq
We could use yq command to remove the status field because the status field is not required when apply the CRD to the kube-apiserver.

[tungbq]

@tungbq We could use yq command to remove the status field because the status field is not required when apply the CRD to the kube-apiserver.

Thanks @jenting. Updated

[jenting]

Nice! Thank you @tungbq

[qiuming-best]

Thanks for your amazing work！ @tungbq