[hoalongnatsu]

What does this PR do?

Makes Kubernetes break investigations stay focused on the selected occurrence,
with a stable log window and an always-present Logs at break panel. Keeps
authorized Workloads inventory usable during synchronization, improves column
alignment, and distinguishes unknown counts from genuinely empty inventory.

• Investigate the break you clicked, including recurring and retained breaks,
  rather than silently switching to another occurrence for the same resource.
• Keep the log-window bracket, selected marker and filters stable as evidence
  loads. Explain missing timestamps, unavailable captures and empty logs instead
  of making the panel disappear.
• Read focused changes and crashes together without Page/Previous/Next controls.
  Bounded loading reports incomplete coverage; cluster lists retain pagination.
• Keep authorized rows and known counts visible during temporary refresh
  failures, including a first usable partial result. Show unavailable counts
  honestly instead of displaying misleading zeros.
• Recover automatically from temporary preparation delays. When recovery is
  exhausted, show an explicit retry rather than a permanent loading skeleton.
• Remove deleted resources when a new inventory is committed. If inventory
  changes invalidate a page, offer to restart paging rather than repeat rows.
• Align Workloads headers and cells across resource kinds, whether or not a
  row supports Logs. Preserve compact mobile layouts and separate row actions.
• Continue clearing protected data when credentials or permissions are revoked.

Why?

Responders should not lose the selected break, its evidence, or useful workload
inventory while the cluster refreshes. Missing data must be distinguishable from
an empty result, and temporary collection failures must not resurrect deleted
resources or make a partial inventory unusable.

This changes the existing investigation experience; it does not add continuous
log storage, new learning workers, or new history-retention policies.

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

Checklist

• 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)