Replace VisualizerOverrides boolean indicator components about rerun HOT 2 OPEN

I like it! In particular the per Visualizer interaction via the FallbackProvider system is rather charming.
Don't know why we rolled up changing the indicators themselves again, probably size considerations?

If a view-level default was provided explicitly, we would use it.

if this is rare enough we could even do that on a per visualizer basis using data conveyed via the ViewState as we do in some other places. Meaning we don't have to formalize this.

from rerun.

Indicators are currently valueless. They are always logged as null, and as such their only purpose is to force the inclusion of a particular magic component-name into the list of components that exist on an entity path.

This means you can never clear an indicator. Once it's been logged it will always be present.

No opinion on the topic of valued indicators themselves, and not sure whether that's relevant here, but adding more context just in case: indicator components are currently logged as an array of null values whose length is the same as the primary/required component on that row (which is free because of how null arrays are encoded). And that length becomes zero if the indicator gets cleared as part of a legacy cascaded clear.

We've made the choice to never actually look at the data for indicators, but technically one could already check the length today and know whether the indicator has been cleared or not.

Obviously very related to query-time clears and the whole discussion about missing data vs. cleared data vs. empty data etc.

from rerun.