[hoalongnatsu]

What does this PR do?

Expands Kubernetes break evidence beyond OOMKilled and adds a durable crash
journal with paged observations and details.

• Show configuration, startup, image, scheduling, eviction, init-container,
  Job, node-health and probe-warning evidence alongside workload breaks.
• Distinguish distinct affected pods from lifetime restart totals, and actual
  termination signals from exit-code hints. Restarts are not counts of a
  particular failure reason.
• Avoid marking a healthy workload broken solely because a terminal pod
  remains after recovery; keep that pod's evidence available when relevant.
• Retain captured crash observations after pod deletion and Versus restarts.
  Page through retained observations and open their details, separately from
  compact summary limits.
• Separate the observation window from the actual termination finish time.
  History defaults to 24 hours by observation time, subject to capacity limits;
  capture gaps, incomplete reads and retention loss remain explicit. This is
  not a record of every Kubernetes event or every unseen crash.

Why?

Responders need to understand why a workload broke without treating every
failure as an OOM kill or opening logs first. Clear counts and retained history
keep investigations useful after pods disappear without overstating coverage.

Type of change

• Bug fix (non-breaking)
• New feature (non-breaking)
• Breaking change (config / API / default behavior)
• Documentation only
• Refactor (no functional change)
• CI / build / chore

Compatibility: evidence counts now mean distinct pods rather than containers.
Consumers relying on the previous count meaning must adjust; no configuration
change is introduced by this enhancement.

Checklist

• go test ./... passes locally
• go vet ./... is clean
• Added or updated tests for the change
• Updated user-facing docs under src/ if behavior changes
• Updated ROADMAP.md if this closes a roadmap item
• No secrets, tokens, or webhook URLs introduced in source / YAML
• No new third-party dependencies (or justified in the description)

User-facing docs are intentionally unchanged in this task; no roadmap closure is claimed. The dependency statement applies only to this crash-evidence enhancement, not earlier timeline work.