Standardize time fields from DPA when API version updates

[mateusoliveira43]

There are several time fields in DPA, some being

• spec.configuration.velero.args.backup-sync-period
• spec.configuration.velero.args.default-backup-ttl
• spec.configuration.velero.args.default-item-operation-timeout
• spec.configuration.velero.args.default-repo-maintain-frequency
• spec.configuration.velero.args.fs-backup-timeout
• spec.configuration.velero.args.garbage-collection-frequency
• spec.configuration.velero.args.item-operation-sync-frequency
• spec.configuration.velero.args.resource-timeout
• spec.configuration.velero.args.store-validation-frequency
• spec.configuration.velero.args.terminating-resource-timeout
• spec.configuration.nodeAgent.timeout
• spec.backupLocations[].velero.backupSyncPeriod
• spec.configuration.velero.defaultItemOperationTimeout
• spec.configuration.velero.resourceTimeout

And they are typed as string, metav1.Duration and time.Duration.

They should be all be the same type, for improved user and developer experience. They should also be validated in validators.

[weshayutin]

well also cross reference with the value expected from velero I think

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kaovilai]

/lifecycle frozen