fix(k8s): include entity kind/name in kubectl timeout error message

[breezy-devs]

Fixes #3686

Problem

When kubectl apply timed out, the error message only reported the duration:

Killed kubectl. Hit timeout of 10s.

This gave no indication of which resource caused the timeout, making it hard to diagnose in deployments with many resources.

Additionally, the condition that triggered this error path was checking wgCtx.Err() for context.DeadlineExceeded, but wgCtx is an errgroup context that only ever emits context.Canceled — never context.DeadlineExceeded. This made the timeout error message completely unreachable.

Fix

1. Fix the condition to check err instead of wgCtx.Err(), so the timeout error is actually returned when escalatingUpdate times out
2. Include the entity's kind and name in the error message

The message now reads:

Killed kubectl. Hit timeout of 10s applying Deployment/my-app.

Test

Added TestTimeoutErrorMessage to verify the error message includes the timeout duration and the entity kind/name.