feat(tree): Schema validation

[alexvy86]

Description

Builds on top of #20904, to enable content being inserted into a shared tree to be validated against the stored schema of the tree.

Reviewer Guidance

The review process is outlined on this wiki page.

I first tried putting the flag that defines if schema validation should happen or not just in TreeConfiguration but some code paths didn't seem to have good access to it. It felt natural to make it part of the policy.

[msfluid-bot]

⯅ @fluid-example/bundle-size-tests: +3.8 KB

Metric Name	Baseline Size	Compare Size	Size Diff
aqueduct.js	453.18 KB	453.18 KB	■ No change
azureClient.js	550.61 KB	550.61 KB	■ No change
connectionState.js	680 Bytes	680 Bytes	■ No change
containerRuntime.js	257.02 KB	257.02 KB	■ No change
fluidFramework.js	357.56 KB	359.46 KB	⯅ +1.9 KB
loader.js	132.89 KB	132.89 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.94 KB	518.94 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.55 KB	359.45 KB	⯅ +1.9 KB
Total Size	3.19 MB	3.19 MB	⯅ +3.8 KB

---

Baseline commit: 6abe291

Generated by 🚫 dangerJS against 191f1e5

[noencke]

Looks great - approving for what I see. I think you mentioned that you're going to make some changes, so feel free to re-request review when necessary.

[alexvy86]

@noencke new changes in; basically moved the new enableSchemaValidation to a property bag passed to new TreeConfiguration() which required adding ITreeConfigurationOptions to the public API (cc @microsoft/fluid-cr-api). Not sure if this will matter much as #20815 moves forward since it might end up replacing schematize() and have its own API shape (could reuse the new interface, maybe with a new name).