Automate update of vm-operator CRDs

[fabriziopandini]

/kind cleanup

under config/deployments/integration-tests/crds we store a copy of vm-operators CRDs that currently must be updated manually.

in order to improve this, we can use the same machinery we are using to create test images for the vm-operator, which are cloning the repo in a temporary folder

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[chrischdi]

/remove-lifecycle stale