Update build-tools and type tests

[CraigMacomber]

Description

#21070 made some improvements to type tests which were needed to regenerate the type tests for client. This change integrates that, as well as regenerates the type tests with the new generator.

Reviewer Guidance

The review process is outlined on this wiki page.

[msfluid-bot]

⯅ @fluid-example/bundle-size-tests: +486 Bytes

Metric Name	Baseline Size	Compare Size	Size Diff
aqueduct.js	453.18 KB	453.18 KB	■ No change
azureClient.js	550.29 KB	550.5 KB	⯅ +220 Bytes
connectionState.js	680 Bytes	680 Bytes	■ No change
containerRuntime.js	257.02 KB	257.02 KB	■ No change
fluidFramework.js	357.54 KB	357.56 KB	⯅ +22 Bytes
loader.js	132.78 KB	132.78 KB	■ No change
map.js	41.45 KB	41.45 KB	■ No change
matrix.js	143.67 KB	143.67 KB	■ No change
odspClient.js	518.83 KB	518.83 KB	■ No change
odspDriver.js	97.29 KB	97.29 KB	■ No change
odspPrefetchSnapshot.js	42.15 KB	42.15 KB	■ No change
sharedString.js	160.19 KB	160.19 KB	■ No change
sharedTree.js	357.53 KB	357.55 KB	⯅ +22 Bytes
Total Size	3.19 MB	3.19 MB	⯅ +486 Bytes

---

Baseline commit: 617ef08

Generated by 🚫 dangerJS against 7d304e5

[Abe27342]

ping me when primary reviewer has approved, merge-tree changes are fine.

[alexvy86]

Per offline discussion, all the already broken types seem to be expected.

For future reference, I think we could handle server separately for type-test update purposes given its separate versioning story. The changes here seem ok to me though.

[alexvy86]

Unrelated to the PR, but this example seems to be the only one with a dependency on build-cli and I don't see it using it (no calls to flub for example). I kind of expected it to be doing type tests because it's still consumed by our partners, but they're disabled. @ChumpChief @tylerbutler do you know if this should be doing type tests or we disabled them on purpose?

There's a few other examples in the same situation. I'll see about removing the dep in all of them outside this PR.

[CraigMacomber]

build cli is used to generate the type tests, so lots of things have it, but maybe this one is unneeded.

Generally example apps have no reason to have type tests, but I'm not sure whats going on with this package though, as its in @fluid-example, but is not private, has exports, and is not imported in any other examples.

[tylerbutler]

Table-document is used by internal partners for historical reasons. It is extremely unique and breaks a lot of "rules" regarding npm scope and supportability. @ChumpChief and @anthony-murphy might know more. There might also be some comments in the fluid-build config file.