Add Container Event Notification for CRI's Update*Resources Interface to Support In-Place Pod Resizing

[HirazawaUi]

The current evented PLEG implementation in CRI generates container events (create/start/stop/delete) to trigger syncPod, but it fails to accommodate the in-place pod resizing feature. During in-place pod resizing, after completing container resource updates via UpdateContainerResources/UpdatePodSandboxResources, we need to re-trigger syncPod to update the container status.

In the generic PLEG implementation, this is achieved by forcing a synthetic container event during the next PLEG relist after doPodResizeAction, which triggers syncPod. However, for evented PLEG (where events originate directly from the container runtime via CRI), there is no native event generated when resource updates occur. Currently, In PR #131024, I implemented a temporary workaround by simulating container runtime-generated events to achieve this behavior. While this approach unblocks testing, it remains a short-term fix.

To fully align with evented PLEG's design, we need container runtimes to emit a dedicated "Update" event when their UpdateContainerResources or UpdatePodSandboxResources CRI interfaces are invoked. This event should notify the Kubelet to trigger syncPod, ensuring consistent behavior between generic and evented PLEG implementations.

/sig node
/kind feature

[HirazawaUi]

/cc @SergeyKanzhelev @tallclair @harche

For Container Runtime maintainer @haircommander @mikebrow

[haircommander]

+1 this sounds good. Maybe we do as part of 1.34 as an extension to evented PLEG (to keep in place resize scope smaller)

[mikebrow]

+1 this sounds good. Maybe we do as part of 1.34 as an extension to evented PLEG (to keep in place resize scope smaller)

^^ this

[HirazawaUi]

/assign

[ffromani]

/triage accepted
/priority important-longterm

there is quick consensus this is real and desirable. Priority subject to revision once we begin the 1.34 cycle