feat(aqueduct): Tree-based PureDataObject implementation

[Josmithr]

Adds a new (internal) PureDataObject implementation backed by a SharedTree, rather than a SharedDirectory.

This implementation was partially derived from an existing prototype in tree-react-api. That package and the example built on it (inventory-app) have been updated to utilize these APIs.

AB#29396

[CraigMacomber]

This will show up in two places based on our release process: the changelog of the package (its fine for that) and the release notes for the client release this lands in.

I think the phrasing here needs to be made a bit more specific, so it makes sense in that context.

Also this description covers a bit too much internal implementation details for a customer facing release.

Suggested change

	Update data object APIs to leverage new SharedTree-based data object class
	Rather than leveraging a classic `DataObject` with a `SharedDirectory` at the root, and a `SharedTree` beneath, the library now leverages a new data object class that uses the `SharedTree` directly at the root.
	Results in some simplifications to this package's APIs which are breaking.
	Namely,
	- Removes the `key` property from the data object configuration.
	This key was used to inform where the SharedTree was parented beneath the root SharedDirectory, so it no longer serves a purpose.
	- Inlined the `ITreeDataObject` interface into `IReactTreeDataObject`.
	Simplify experimental tree data object implementation
	The experimental tree data object from `tree-react-api` are incompatible with their previous version which used a `DataObject` with a `SharedDirectory` at the root.
	The library now leverages a new data object that uses the `SharedTree` directly at the root.
	In addition to breaking compatibility with existing documents, This resulted in some simplifications to the APIs which are also breaking:
	- Removes the `key` property from the data object configuration.
	This key was used to specify where the SharedTree was parented beneath the root SharedDirectory.
	- Inlined the `ITreeDataObject` interface into `IReactTreeDataObject`.

[Josmithr]

Good feedback. I made some adjustments to your suggestion, so let me know what you think of the final wording.

[github-actions]

🔗 Found some broken links! 💔

Run a link check locally to find them. See
https://github.com/microsoft/FluidFramework/wiki/Checking-for-broken-links-in-the-documentation for more information.

linkcheck output

> fluid-framework-docs-site@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

http://localhost:3000/docs/data-structures/tree
- (36:97) 'the Shar..' => http://localhost:3000/docs/api/tree (HTTP 404)

http://localhost:3000/docs/data-structures/tree/
- (36:97) 'the Shar..' => http://localhost:3000/docs/api/tree (HTTP 404)

http://localhost:3000/docs/data-structures/tree/schema-definition
- (30:128) 'SharedTr..' => http://localhost:3000/docs/api/tree (HTTP 404)

http://localhost:3000/docs/start/tree-start
- (44:4) 'the API ..' => http://localhost:3000/docs/api/tree/schemafactory-class (HTTP 404)
- (61:7) 'the API' => http://localhost:3000/docs/api/tree/treechangeevents-interface (HTTP 404)


Stats:
  162291 links
    1317 destination URLs
    1549 URLs ignored
       0 warnings
       3 errors

 ELIFECYCLE  Command failed with exit code 1.