Support node draining by external NVIDIA maintenance OP

[heyvister1]

SRIOV OP internal drain controller can be disabled, through USE_MAINTENANCE_OPERATOR_DRAINER, and draining will be performed by external NVIDIA maintenance operator

Cherry-picked from upstream #952

[github-actions]

Thanks for your PR,
To run vendors CIs, Maintainers can use one of:

• /test-all: To run all tests for all vendors.
• /test-e2e-all: To run all E2E tests for all vendors.
• /test-e2e-nvidia-all: To run all E2E tests for NVIDIA vendor.

To skip the vendors CIs, Maintainers can use one of:

• /skip-all: To skip all tests for all vendors.
• /skip-e2e-all: To skip all E2E tests for all vendors.
• /skip-e2e-nvidia-all: To skip all E2E tests for NVIDIA vendor.
  Best regards.

[almaslennikov]

LGTM, let's address the utests failure before merging

[coveralls]

Pull Request Test Coverage Report for Build 18373938486

Details

• 4 of 4 (100.0%) changed or added relevant lines in 1 file are covered.
• 4 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.1%) to 62.082%

---

Files with Coverage Reduction	New Missed Lines	%
controllers/helper.go	4	70.57%

Totals
Change from base Build 18361383049:	0.1%
Covered Lines:	8712
Relevant Lines:	14033

---

💛 - Coveralls

[rollandf]

@heyvister1 do we push cherry-pick to master?

[heyvister1]

@heyvister1 do we push cherry-pick to master?

I didn't use git cherry-pick, rather than created a new PR for SRIOV under Mellanox org

[rollandf]

@heyvister1 do we push cherry-pick to master?

I didn't use git cherry-pick, rather than created a new PR for SRIOV under Mellanox org

My question is more about to which branch we should push our PRs?

[heyvister1]

@heyvister1 do we push cherry-pick to master?

I didn't use git cherry-pick, rather than created a new PR for SRIOV under Mellanox org

My question is more about to which branch we should push our PRs?

Changed it to v25.10.x branch

[heyvister1]

/test-all