Make visible time range ui aware of latest-at & QueryRange

[Wumpf]

What

Under the hood this is now actually a "query range" ui since it operates directly on QueryRange, but I opted to not call it that in the viewer yet.

The user facing changes are rather subtle

Before:
Defaulting to latest-at:

Defaulting to single timestamp:

After:
Defaulting to latest-at:

Defaulting to single timestamp:

Note that today latest-at can only be inherited (via default). You can't actually set it as an override yet (we decided to delay that a bit since it needs even more restructuring and imho we may want to constrain that depending on the view type).

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.

[Wumpf]

there's a grammar messup / typo in the tooltip depicted on the last screenshot