feat(devtools-core): Render ST's Visualizer to Include Root Field's Allowed Types

[jikim-msft]

Description

26472

The current visualization generation logic in DefaultVisualizers.ts treats the root of the shared tree as a node and thus omits information that should be included in the root of the ST visualizer. Since the root field is allowed to have multiple types (i.e., different schema or primitive types), this information should be rendered in the tooltip of the visualizer.

This PR changes how the visualizer renders the allowed types in the tooltip

Example Schema

const config = new TreeViewConfiguration({
			schema: [RootNodeOne, RootNodeTwo, builder.string, builder.number],
		});

Before

After
Defined

Undefined

[Josmithr]

I left a handful more comments, but overall this is looking really great! I suspect it will be ready for approval after you address these few comment.

[jikim-msft]

@Josmithr

Unlike coupling the allowedTypes and isRequired in visualizeSharedTreeBySchema(), I decided to leave these two parameters separately, since it isn't the entry point for the ST visualizer and I thought the doc describes when the requirements can be undefined.

Interested in your thought.

[Josmithr]

Well, you could combine the properties differently in this case, which might be a bit cleaner. E.g.,

fieldSchemaProperties: Record<string, FieldSchemaProperties>

Where you have a single record, instead of 2, that maps the field key to both of the relevant properties.

[alexvy86]

Do the properties here need to be optional?

[jikim-msft]

I wanted it to align with the optionality of VisualSharedTreeTypes.ts (SharedTreeSchemaNode). Hence, marked it optional since non-ST VisualNodes do not need allowed types at the moment.