fix: fail backup early when CSI VolumeSnapshot error persists in async poll

[priyansh17]

Please add a summary of your change

• This bug can be reproduced by triggering a scenario where cloud snapshot provisioning fails (e.g., make Azure Disk run out of available capacity or permissions).
• The problematic code path is in pkg/backup/actions/csi/volumesnapshot_action.go, in the Progress() method of volumeSnapshotBackupItemAction:

if boolptr.IsSetToTrue(vs.Status.ReadyToUse) {
    // ... continue to check VSC
} else if vs.Status.Error != nil {
    errorMessage := ""
    if vs.Status.Error.Message != nil {
        errorMessage = *vs.Status.Error.Message
    }
    p.log.Warnf("VolumeSnapshot has a temporary error %s. Snapshot controller will retry later.", errorMessage)
    return progress, nil  // <-- Returns NOT completed, no error propagated
}

• This returns progress.Completed=false even for permanent errors, so the backup controller keeps polling Progress() for the full itemOperationTimeout (could be hours), instead of failing immediately.
• The synchronous code path (WaitUntilVSCHandleIsReady) properly fails on timeout, but async Progress() does not.

The fix is to wait for a certain period of time before failing it/ skipping it.

Does your change fix a particular issue?

Fixes #(issue)
#9674

Please indicate you've done the following:

• Accepted the DCO. Commits without the DCO will delay acceptance.
• Created a changelog file (make new-changelog) or comment /kind changelog-not-required on this PR.
• Updated the corresponding documentation in site/content/docs/main.

[codecov]

Codecov Report

❌ Patch coverage is 48.14815% with 42 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
pkg/controller/backup_controller.go	6.89%	27 Missing ⚠️
pkg/util/csi/volume_snapshot.go	23.52%	10 Missing and 3 partials ⚠️
pkg/cmd/cli/schedule/create.go	0.00%	1 Missing ⚠️
pkg/cmd/server/server.go	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[kaovilai]

fyi this is in draft, when ready for review mark it as ready

[blackpiglet]

@priyansh17
Do we need a snapshot error timeout timer per backup?
If not, I suggest to use a global timer instead.