Connect native onboarding to server state and hide internal datasets

[VibeSWE]

The native setup guide already provides ingestion, exploration and team links, but does not consume the existing server checklist. The dataset inventory resolves telemetry types without distinguishing internal streams.

Integrate the Prism home response into the existing guide and exclude internal datasets consistently from normal inventory and selectors. Reuse its includeInternal behavior or authoritative stream metadata; preserve log/metric/trace routing rather than filtering by dataset names.

Acceptance criteria

• Checklist state refreshes from the authenticated server, with clear loading, error and demo states.
• data_ingested reflects stored events in datasets the response includes (by default, listable non-internal datasets), not recent arrival. Keep the existing ingestion-verification flow.
• Present user_added as tenant-level team state, not proof that the viewer invited someone. alert_created reflects alerts visible to the viewer. Respect permissions when offering team/alert actions.
• Omit keystone_created, which is currently hardcoded false.
• Internal datasets are excluded consistently from shared inventory and pickers; permitted user datasets retain correct telemetry routing. Test fresh deployments, legacy internal datasets and restricted users.

Filtering must not replace authorization or delete stored data. Decide how administrators intentionally inspect internal datasets. Startup/storage cleanup remains separate in pmeta discussion #35.

Suggested order: first; builds on existing UI and backend capabilities.