[hoalongnatsu]

What does this PR do?

Makes Kubernetes investigations easier to navigate and keeps cluster views
complete at larger sizes. Responders get a quieter interface, a focused
Timeline and reliable resource context without size-related partial warnings.

• Complete cluster views: inventory and metrics collect in the background
  without fixed record/page cutoffs. Views use cached data, show a clear initial
  syncing state and retain the last good data when a refresh fails.
• Focused Timeline: a chronological, virtualized list of changes, breaks
  and crashes replaces the crowded default chart. Select a break for its chart
  and logs; page through history without mixing independently ordered lists.
• Relevant relationships: Related includes the selected resource's owners,
  children, traffic connections and dependencies, not other workloads merely
  sharing a Secret or ConfigMap.
• Less clutter: one quiet coverage indicator replaces repeated caveats.
  Topology counts, CPU/memory controls and long-name Uptime tiles fit desktop
  and mobile layouts.
• Clear navigation: Workloads follows Overview; namespace filters offer
  searchable choices; Current · Previous makes returning to live logs obvious.
• Actionable alert settings: enabling issue alerts requires an enabled
  channel. Authorized users can still turn alerts off after channels are
  disabled; a missing public URL does not block delivery.

Collection completeness does not remove log-admission limits, history retention
or permissions. Refused reads and real refresh failures remain visible.

Why?

Large clusters exposed crowded history, unrelated resources and repeated
machine-facing warnings. Responders need to find the relevant evidence quickly
without wondering whether a count is incomplete or how to return to live logs.

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

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