✨ Add supports to Crypto Spec in VMOp VirtualMachine and PVC

[laozc]

What this PR does / why we need it:

Add new fields to opt-in EncryptionClass name on volumes

    // +optional
    EncryptionClassName *string `json:"encryptionClassName,omitempty"`

and VMOp.Crypto

    // Crypto describes the desired encryption state of the VirtualMachine.
	// +optional
	Crypto *VirtualMachineCryptoSpec `json:"crypto,omitempty"`

VirtualMachineCryptoSpec.Crypto

type VirtualMachineCryptoSpec struct {
   EncryptionClassName *string `json:"encryptionClassName,omitempty"`
   UseDefaultKeyProvider *bool `json:"useDefaultKeyProvider,omitempty"`
}

Note: The EncryptionClassName changed to use *string because of the API lint in CAPV.

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 #

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sbueringer for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[zjs]

Overall, LGTM