Stop building invalid type syntax for hover and code fixes - #65502

The node builder and the missing-type-annotation code fix could build
type nodes containing syntax that is not valid in those positions:
expressions in place of types, property-access expressions as typeof
names, type parameter declarations in type argument lists, and type
arguments in type parameter lists. These trees reach API consumers and
every caller that expects valid syntax, so the printer accepted
property accesses as entity names, and instantiation expressions were
classified as type nodes to let them through.

Most of this came from notation that hover shows but that is not valid
type syntax: f<string>.C for a class local to a generic function, outer
type parameters with their constraints and defaults in names such as
C<out T extends string = "a">.prototype, and instantiated arguments in
place of a signature's type parameters, as in <string>(value: string).

Build valid syntax instead, and record the hover notation as
emit-context metadata that the printer substitutes. An instantiated
signature still declares its remaining type parameters, but those
declarations are not printed, so they do not count toward the
truncation length. Hover formatting uses a builder local to the
operation so that its display metadata is not retained by the
checker's cached builder.

Classified hover colors each name by looking up the symbol recorded for
its identifier. Display notation such as
foo<void>.X.m<number, boolean>.(Anonymous function)<Date>.Y<string> is
assembled from copies of earlier display expressions, and those copies
had no recorded symbols, so most of the names printed as plain text.

Copy the symbols along with every identifier in a copied display
expression.

Display expressions are synthesized and only printed, so they can share
nodes with each other and with the type tree. Sharing keeps each
identifier's recorded symbol for classified hover without copying.

Instantiated signatures used for display print their arguments in place
of the type parameters, so build the arguments alone for them. Hover is
the only consumer; the checker's public entry points clear the
hover-only flags.

The printer prints a display type parameter through its type
reference, so type argument lists need no separate hook.

The checker reuses one node builder for type, symbol and signature
formatting. Display entries recorded on its emit context stayed for the
checker's lifetime, so repeated hovers kept adding to it.

Store display entries in their own table and clear it when the
outermost operation releases the builder. Serialized types that use
display notation are not cached, because a cached copy would outlive
those entries. Every formatting path can then share the builder.