Search APIs don't properly resolve Component Selector against remote schema

[jleibs]

The Vector/FTS Search APIs currently have inconsistent hacks that only sometimes do the right thing.

See, for example:

rerun/rerun_py/src/catalog/dataset.rs

Lines 227 to 232 in bc0e318

	// TODO(jleibs): get rid of this hack
	if component_descriptor.component_name == ComponentName::from("rerun.components.Text") {
	component_descriptor = component_descriptor
	.or_with_archetype_name(|| "rerun.archetypes.TextLog".into())
	.or_with_archetype_field_name(|| "text".into());
	}

The reasoning behind this is that the server needs to know the exact column to build the index over and search.

Now that we have an API to get the schema, we can do much better.

The logic should now be:

• Get the schema for the dataset
• Scan the schema to find a SINGLE match for the component selector
  • If there are no matches, or multiple matches this should raise an error about an ambiguous component selector.
  • Note: tagged components are going to create situations that will be inherently ambiguous (follow up with @Wumpf to make sure we are considering this in the tagged component workstream -- component Selectors will need to be expanded to be tagged-component aware.)

This logic needs to be replicated in all of:

• create_fts_index
• create_vector_index
• fts_search
• vector_search

This probably means writing some helper on dataset like resolve_component_selector. There is some similar logic for view contents now in dataframe_query.rs`.