Bump server in client with prerelease packages

[jatgarg]

Description

Bump protocol-definitions, server-services-client, server-local-server, protocol-base, server-services-core, server-test-utils, and gitresources, tinylicious package versions in client repo.

Modified the ISnashotTree to add a prop: omitted to let service communicate to client whether it omitted the contents or not.
This change was made in protocol-defn package which was upgraded in server repo, and now upgrading server and protocol defn packages in client repo.

This is related to Data Virtualization.

[msfluid-bot]

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

Metric Name	Baseline Size	Compare Size	Size Diff
aqueduct.js	511.94 KB	511.98 KB	⯅ +44 Bytes
connectionState.js	680 Bytes	680 Bytes	■ No change
containerRuntime.js	244.62 KB	244.64 KB	⯅ +22 Bytes
loader.js	170.65 KB	170.67 KB	⯅ +22 Bytes
map.js	46.53 KB	46.54 KB	⯅ +11 Bytes
matrix.js	148.88 KB	148.9 KB	⯅ +11 Bytes
odspDriver.js	97.67 KB	97.7 KB	⯅ +33 Bytes
odspPrefetchSnapshot.js	42.63 KB	42.65 KB	⯅ +22 Bytes
sharedString.js	168.61 KB	168.62 KB	⯅ +11 Bytes
sharedTree.js	334 KB	334 KB	■ No change
Total Size	1.87 MB	1.87 MB	⯅ +187 Bytes

---

Baseline commit: 55806cb

Generated by 🚫 dangerJS against 88e641a

[tylerbutler]

I suggest not doing prereleases of server. It's a time bomb that will blow up for the person who has to do a server release before they can release client. Because server releases can contain all sorts of changes and the longer we leave it the changes will pile up and become a major hassle for the person who has to do the real server release.

If you need a server change, do a full server release, major version, and bump the client to use it.

[tylerbutler]

That said, since the prerelease was already done, carry on. Maybe for next time, though, do a full server release.