Use weaker version of ComponentDescriptor for indicators

[grtlr]

Related

• Part of Tagged components #6889.
• From Use ComponentDescriptor in HybridLatestAtResult #9938 (comment):

was curious and poked a lil bit into the ci failure: took me a while to notice but the primary issue presented by the failing images is that it draws lines instead of points.

Which implies an issue with indicators (wtf why is that the only test failing then.. but sure usually there's no choice; have only a vague hunch about that :/). Looking at impl<A: Archetype> crate::ComponentBatch for GenericIndicatorComponentArray<A> indicators are never logged with their full descriptor, but are advertised as such.

So I quickly hacked the generated SeriesPoints::descriptor_indicator to be name only and sure enough that fixed the test. What to do about this knowledge? Uhm.. yeah... that is definitely a Monday problem 😄

What

Because indicators are about to go away soon (™️) anyways, making them weaker (qualification-wise) is probably the easiest choice.

Doing this in a separate PR to help with potential git bisect in the future.

[github-actions]

Web viewer built successfully. If applicable, you should also test it:

• I have tested the web viewer

Result	Commit	Link	Manifest
✅	3926775	https://rerun.io/viewer/pr/9990	+nightly +main

^{Note: This comment is updated whenever you push a commit.}

[Wumpf]

thanks for separating it out 👍

[Wumpf]

actually, let's be a little bit more thorough to avoid surprises during this week - we should do the same in C++ and Python

[grtlr]

It looks like C++ is only using the component_name for indicators already. I think the Python code, will also do the correct thing via the Rust-bindings.