Expose PlotLegend and ScalarAxis (axis_y) properties on TimeSeriesView blueprint

[Wumpf]

What

• Part of #6083

Usage example:

# ...
            # Plot with custom Y range that is locked into place during zoom and legend at the bottom left.
            rrb.TimeSeriesView(
                origin="/plot",
                axis_y=rrb.ScalarAxis(range=[0, 1], lock_range_during_zoom=True),
                plot_legend=rrb.Corner2D.LeftBottom,
            ),
            # Hide plot legend
            rrb.TimeSeriesView(
                origin="/plot",
                plot_legend=rrb.PlotLegend(visible=False),
            ),
# ...

Changed codegen type definition:

/// A time series view.
table TimeSeriesView (
    "attr.rerun.view_identifier": "TimeSeries"
) {
    /// Configures the vertical axis of the plot.
    axis_y: rerun.blueprint.archetypes.ScalarAxis (order: 1000);

    /// Configures the legend of the plot.
    plot_legend: rerun.blueprint.archetypes.PlotLegend (order: 2000);
}

Added the necessary serialization code and snippets. More aggressively using datatypes now to reduce amount of serialization code we need to write in Python.

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.

[github-actions]

Deployed docs

Commit	Link
8ba76cd	https://landing-oq8fyro82-rerun.vercel.app/docs

[emilk]

Remember to describe in the PR how a user can set these properties from code. They will want to know when they click the PR link in the changelog!

[emilk]

Why would we sometimes prefer bool over rerun.datatypes.Bool and the other way around?

[Wumpf]

Should always prefer it in Components. We want to get to a place where components always forward to a datatype. Not only will this get us closer to a place where components are a thin semantic layer, it also means I don't have to implement bool serialization again and again in Python (and it won't be generated either for C++, Rust is the odd one out where we regenerate a lot of stuff all the time, to be fixed).
We're not consequent in this yet, but it's already happening e.g. with PanelExpanded

[emilk]

I wonder who has the type-sensitive sorter. I guess we'll find out in a PR soon enough

[Wumpf]

Nope, we won't 😆

• Remove handwritten __all__ python definitions #6117

[Wumpf]

added usage example that we can then also use for snippets. Also improved ergonomics to make this possible in the first place