Implement storage migration logic

[awels]

What this PR does / why we need it:
Renamed migplan and migmigration to storagemigplan and storagemig. Renamed the CRDs to match the new names.
Added unit tests for the storage mig plan and storage migration logic.
Added kubevirt and CDI CRDs to the test environment.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

[awels]

/cherry-pick release-1.7

[awels]

/cherry-pick release-1.6

[kubevirt-bot]

@awels: cannot checkout release-1.7: error checking out "release-1.7": exit status 1 error: pathspec 'release-1.7' did not match any file(s) known to git

Details

In response to this:

/cherry-pick release-1.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kubevirt-bot]

@awels: cannot checkout release-1.6: error checking out "release-1.6": exit status 1 error: pathspec 'release-1.6' did not match any file(s) known to git

Details

In response to this:

/cherry-pick release-1.6

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.