Description of problem:
When creating a PVC from the UI, the created DV is using the PVC API (and not the storage API).


Version-Release number of selected component (if applicable):
CNV 4.10.0, OCP 4.10.0-fc.0

How reproducible:


Steps to Reproduce:
1. From the UI, upload a PVC
2.
3.

Actual results:
The created DV is using the PVC API (and not the storage API).

Expected results:
Storage API should be used

Additional info:
Name:         centos8
Namespace:    default
Labels:       kubevirt.ui/cdrom=false
Annotations:  cdi.kubevirt.io/storage.bind.immediate.requested: true
API Version:  cdi.kubevirt.io/v1beta1
Kind:         DataVolume
Metadata:
  Creation Timestamp:  2022-01-18T10:42:26Z
  Generation:          66
  Managed Fields:
    API Version:  cdi.kubevirt.io/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:cdi.kubevirt.io/storage.bind.immediate.requested:
        f:labels:
          .:
          f:kubevirt.ui/cdrom:
      f:spec:
        .:
        f:pvc:
          .:
          f:accessModes:
          f:resources:
            .:
            f:requests:
              .:
              f:storage:
          f:storageClassName:
          f:volumeMode:
        f:source:
          .:
          f:upload:
    Manager:      Mozilla
    Operation:    Update
    Time:         2022-01-18T10:42:26Z
    API Version:  cdi.kubevirt.io/v1beta1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:conditions:
        f:phase:
        f:progress:
    Manager:         virt-cdi-controller
    Operation:       Update
    Time:            2022-01-18T10:42:26Z
  Resource Version:  4366120
  UID:               5d3e5ba8-b854-4421-96a2-1601f1e2f31b
Spec:
  Pvc:
    Access Modes:
      ReadWriteOnce
    Resources:
      Requests:
        Storage:         20Gi
    Storage Class Name:  hostpath-provisioner
    Volume Mode:         Filesystem
  Source:
    Upload: