Scheduler Preemption for In-Place Pod Resize

<!-- This section is incredibly important for producing high-quality, user-focused documentation such as release notes or a development roadmap. It should be possible to collect this information before implementation begins, in order to avoid requiring implementors to split their attention between writing release notes and implementing the feature itself. KEP editors and SIG Docs should help to ensure that the tone and content of the Summary section is useful for a wide audience. A good summary is probably at least a paragraph in length. --> In-Place Pod Resize reached GA in 1.35, allowing pod resizing without restarts. However, unlike traditional pod recreation, in-place resizes that exceed node capacity do not currently trigger the preemption of lower-priority pods. Instead, they remain in a Deferred resize status and require manual intervention. We propose that the Scheduler actively creates space for resize requests by preempting lower-priority pods, following the same preemption logic used when scheduling new pods.