Introduce a TimeSeries archetype and use it to control the plot legend

[jleibs]

What

This is the basic pattern we expect to see for all of these view-configuration type tasks:

• Add a new archetype / component
• Add logic to the TimeSeries space-view-class implementation that both reads and writes the components directly from the blueprint store.

This generally seems to be much easier to think about than dealing with the EntityProperties struct as this was handled previously as it's exclusively a contact between the TimeSeries archetype and the TimeSeriesSpaceView implementation.

Open question:

• Should we suffix all our view archetypes with something like TimeSeriesView?

Needs #4609 to land first since I developed there before rebasing to main.

Will be nice to come back and clean this up again once #3384 is done.

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 newly built examples: app.rerun.io
  • Using examples from latest main build: app.rerun.io
  • Using full set of examples from nightly build: app.rerun.io
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG

• PR Build Summary
• Docs preview
• Examples preview
• Recent benchmark results
• Wasm size tracking

[abey79]

LGTM but shouldn't the legend stuff be removed from EntityProperties then?

[jleibs]

LGTM but shouldn't the legend stuff be removed from EntityProperties then?

Still being used separately in the BarChart -- I'll introduce more Archetypes and remove it in a future PR.