Update UI for static components

[abey79]

What

This PR updates the UI to better display static components, including:

• Components logged as static now have a different icon.
• Components logged as static do not have any event displayed in the timeline (see below for possible follow-up work).
• The "timeless" gutter in the timeline is gone.
• The hover tooltip in the streams for static component now displays their content (timeful components have their content displayed on the corresponding event in the timeline).
• All components now have a "logged time" displayed along their data (showing the actually logging time that was taken into consideration by the current LatestAt query). It shows <static> for static components. This appears both in the selection panel and in the hover tooltips.
• In addition, data consistency information is displayed for static component (both tooltip and selection panel):
  • Warning (yellow) if multiple static logs were recorded (the data of previous logging event is overwritten and not recoverable from the datastore).
  • Error (red) if the static component has timeful stuff logged as well (albeit that data is not loss, it's not queryable and extremely likely an indication of user error).

Note: the included release checklist is nice to try the error/warning cases.

• Fixes Update UI for static component #6074
• Possible follow-up Provide a better display of static components in the timeline #6102

Screenshots

static + timeful error:

multi-static warning:

selection panel:

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested the web demo (if applicable):
  • Using examples from latest main build: rerun.io/viewer
  • Using full set of examples from nightly build: rerun.io/viewer
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
• If applicable, add a new check to the release checklist!

• PR Build Summary
• Recent benchmark results
• Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

[teh-cmc]

nice!

[nikolausWest]

@abey79: question on this we never talked about. How do we report the opposite case where someone logged data as timeful first, and then logged as static (in which case I believe we are supposed to ignore the static call)?

[teh-cmc]

(in which case I believe we are supposed to ignore the static call)

static data always take priority, irrelevant of what got logged first.

[abey79]

Yeah. That piece of data would be displayed as a regular timeful thing, and as soon as the static log is ingested by the viewer, its back to the error/warning display of this PR.

[nikolausWest]

static data always take priority, irrelevant of what got logged first.

Ok, great, well that keeps things simpler then