Update KEP-5007 DRA Device Binding Conditions

[KobayashiD27]

• One-line PR description: updating KEP docs

• Issue link: DRA: Device Binding Conditions #5007

• Other comments:

This PR updates KEP-5007 to clarify the scope, motivation, and design of the proposed BindingConditions mechanism.

Key updates include:

• Rewriting the Motivation section to emphasize general applicability beyond CDI, while retaining CDI as a motivating example.
• Refining the Goals section to focus on readiness-aware binding and condition-based scheduling logic, rather than specific device types.
• Rewriting the prioritization logic in the Goals section to describe general scheduling behavior based on BindingConditions.

These changes aim to make the KEP easier to review and better aligned with the feedback received during discussion. Feedback is welcome!

related to : kubernetes/kubernetes#130160

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: KobayashiD27
Once this PR has been reviewed and has the lgtm label, please assign macsko for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• keps/sig-scheduling/OWNERS

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

[k8s-ci-robot]

Hi @KobayashiD27. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[KobayashiD27]

cc @pohly @dom4ha
I've updated the KEP description based on the PR discussion and the current implementation. Could you please take a look when you have a moment?