Support RollingUpdate strategy for SandboxWarmPool template rollouts #426
Description
With #347 we've introduced the concept of update strategies (Recreate and OnDelete) to SandboxWarmPool.
Warm pools exist to eliminate cold-start latency. With the Recreate strategy, when a SandboxTemplate is updated, all stale pods are deleted simultaneously. This means the warm pool has zero available resources until replacement pods are scheduled and running. For upstream applications relying on the warm pool for fast sandbox provisioning, this causes unnecessary latency spikes, directly defeating the purpose of maintaining a warm pool in the first place.
A possible solution could be a RollingUpdate strategy (similar to Deployment rollout behavior) that replaces stale pods incrementally rather than all at once.