Fix DRA enablement logic

[towca]

What type of PR is this?

/kind bug

What this PR does / why we need it:

The DRA scheduler plugin is enabled by default since 1.34. We have to hack it to be disabled if the CA DRA logic is disabled via the flag. Without this, the DRA scheduler plugin is enabled but not set up properly, and panics.

Does this PR introduce a user-facing change?

Cluster Autoscaler no longer panics when the DRA flag is false but there are pending Pods referencing ResourceClaims in the cluster.

[towca]

/cherry-pick cluster-autoscaler-release-1.34

[k8s-infra-cherrypick-robot]

@towca: once the present PR merges, I will cherry-pick it on top of cluster-autoscaler-release-1.34 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick cluster-autoscaler-release-1.34

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[mtrqq]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mtrqq, towca

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• cluster-autoscaler/OWNERS [towca]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-infra-cherrypick-robot]

@towca: new pull request created: #8599

Details

In response to this:

/cherry-pick cluster-autoscaler-release-1.34

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.