Timeless data store with UI override

[emilk]

We want to be able to set blueprint options from the logging SDK, e.g. set the default 3D camera pose or hide/show the 3D axes. Such data is not bound to any timeline.

We also want to be able to override that logged state in the UI.

So we need two timeless stores: one that is part of LogDb, and one that is part of the UI-state. We can then easily reset the UI state to get back to whatever state the user logged.

Any queries to these stores should first check the ui store and then LogDb as a fallback.

Perhaps this should replace our "timeless" thing? Current we only use timeless=true for view coordinates and annotation context. Should the timeless store be completely separate from the time-store?

[emilk]

Discuss during the meetup in two weeks

[emilk]

We now support UI/blueprint overrides