Podman CLI sub‑command cancellation and timeout handling inconsistency

Podman CLI offers the `--stop-timeout` flag for pods and containers, defining a maximum wait period before a forced kill, and the `--time` flag for `podman run` to cap container lifetime.

Sub‑commands such as `podman generate` or `podman build` receive SIGTERM but lack an explicit abort mechanism, often resulting in abrupt termination that bypasses timeout enforcement.

The behavior varies with Podman version; releases before 2.0 treat `--stop-timeout` as a soft limit, and runtime selection (crun, runc, custom) influences signal propagation reliability.

What behavior should SIGTERM propagation exhibit for sub‑commands across Podman versions? Is a unified cancellation flag or API planned to enforce timeout limits uniformly? How does runtime choice affect the reliability of graceful cancellation?