Regenerate CRDs for the sourceSize status field (#10516)

#10506 added SourceSize to the PodVolumeBackup and DataUpload status
types but did not regenerate the CRD manifests. Without the field in the
CRD schema, the API server silently drops status.sourceSize on write, so
the recorded source size never reaches the cluster objects.

Generated with hack/update-3generated-crd-code.sh (controller-gen
v0.16.5).

Signed-off-by: chlins <chlins.zhang@gmail.com>

config/crd/v1/bases/velero.io_podvolumebackups.yaml

@@ -249,6 +249,10 @@ spec:
                 description: SnapshotID is the identifier for the snapshot of the
                   pod volume.
                 type: string
+              sourceSize:
+                description: SourceSize holds the total size of the source volume.
+                format: int64
+                type: integer
               startTimestamp:
                 description: |-
                   StartTimestamp records the time a backup was started.

config/crd/v2alpha1/bases/velero.io_datauploads.yaml

@@ -250,6 +250,10 @@ spec:
                 description: SnapshotID is the identifier for the snapshot in the
                   backup repository.
                 type: string
+              sourceSize:
+                description: SourceSize holds the total size of the source volume.
+                format: int64
+                type: integer
               startTimestamp:
                 description: |-
                   StartTimestamp records the time a backup was started.