fix(dataprotection): wait for Kubernetes PVC binding before restore completion

[leon-ape]

Part 1 of 4 for #10755.

Problem

VolumePopulator used spec.volumeName != "" as the restore-complete signal. That is weaker than the binding contract consumed by Kubernetes scheduling and can release restore resources before the PV controller has completed the binding.

Changes

• wait for both spec.volumeName and pv.kubernetes.io/bind-completed before the first successful release
• apply the binding gate only to the unreleased lifecycle transition so failed and already released PVC states remain idempotent
• use the same binding-complete predicate for serial prepareData and postReady gates
• keep helper resources and Restore=Unknown while formal binding is pending
• preserve the existing PVC Bound status synchronization unchanged; its removal is isolated in chore(dataprotection): leave PVC bound status to Kubernetes #10780

Scope

This PR consumes the Kubernetes binding-complete signal. Restored-PV ClaimRef and populate-from provenance validation is intentionally isolated in #10778. This PR does not add provisioner compatibility handling, Cluster finalizers, cleanup-path refactoring, or change PVC status ownership.

Tests

• full controllers/dataprotection suite (156 Ginkgo specs plus unit tests)
• focused binding-complete, failed-terminal, released-reentry, serial, and postReady tests

Fixes #10755

[apecloud-bot]

Auto Cherry-pick Instructions

Usage:
  - /nopick: Not auto cherry-pick when PR merged.
  - /pick: release-x.x [release-x.x]: Auto cherry-pick to the specified branch when PR merged.

Example:
  - /nopick
  - /pick release-1.1

CLA Recheck Instructions

Usage:
  - /recheck-cla: Trigger a re-check of CLA status for this pull request.
Example:
  - /recheck-cla

[codecov]

Codecov Report

❌ Patch coverage is 92.85714% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 64.93%. Comparing base (3ebf861) to head (b9b7b50).

Files with missing lines	Patch %	Lines
...llers/dataprotection/volumepopulator_controller.go	92.85%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10779      +/-   ##
==========================================
+ Coverage   64.85%   64.93%   +0.08%     
==========================================
  Files         506      506              
  Lines       63316    63323       +7     
==========================================
+ Hits        41062    41121      +59     
+ Misses      18611    18572      -39     
+ Partials     3643     3630      -13     

Flag	Coverage Δ
unittests	64.93% <92.85%> (+0.08%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[leon-ape]

/approve

[leon-ape]

/approve