Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

docs: add DRA safety section to NodeClaim optimization RFC

Document why the optimization pass skips any NodeClaim holding a pod
with ResourceClaim requests: the displaced-pod cost estimator cannot
see devices requested through ResourceClaims, and revert is
independently unsafe because a committed device allocation has no
inverse and RevertTo re-widens InstanceTypeOptions back to the
snapshot superset.

Also note in the split-point section that DRA and strict-mode reserved
offerings short-circuit ahead of the four gates, and record the
narrower split-position carve-out that was considered and rejected.

Signed-off-by: Michael Manders <mmanders@amazon.com>