test(conformance): bound running-delete with a one-second TERM delay #5290

User Story

I maintain OpenShell conformance coverage and need a running-delete regression test that catches the boundary shutdown hang using a controlled workload and a 10-second completion deadline.

Description

Create a sandbox whose workload handles TERM by waiting one second before exiting. Confirm that its handler is installed before deleting it. Require public deletion completion and absence from get and list within one shared 10-second deadline starting before deletion.

Context

Narrow follow-up to #5285. Local Kubernetes experiments distinguish the broken baseline from the boundary fix in #5279. This test does not establish graceful workload shutdown or that all runtime components avoid grace-period SIGKILL. The stronger signal-processing coverage in #5285 remains separate.

Definition of Done

• Add the test to the all-driver conformance lifecycle suite.
• Synchronize on workload readiness after TERM trap installation.
• Bound deletion and get/list absence checks by one 10-second deadline.
• Demonstrate failure on the broken baseline and success with fix(sandbox): bound runtime shutdown after SIGTERM #5279 in the local Kubernetes environment.
• Document the test scope and validation limitations.