Add scopedFactory

[CraigMacomber]

Description

Add SchemaFactory.scopedFactory

Reviewer Guidance

The review process is outlined on this wiki page.

PR Overview

This PR adds a new method, SchemaFactory.scopedFactory, to simplify creating a new SchemaFactory with a nested scope string, enabling better organization and collision prevention for related schemas.

• Introduces the scopedFactory method in the SchemaFactory class for handling nested scopes.
• Updates tests to use the new scopedFactory method instead of manually concatenating scope strings.
• Updates API report files to document the new scopedFactory method.

Reviewed Changes

File	Description
.changeset/grumpy-crabs-hide.md	Specifies version bumps and changelog entry for the new feature.
packages/dds/tree/src/simple-tree/api/schemaFactory.ts	Adds the scopedFactory method implementation with proper JSDoc comments.
packages/dds/tree/src/test/simple-tree/api/schemaCreationUtilities.spec.ts	Updates tests to utilize the new scopedFactory method.
Various API report files	Documents the new scopedFactory method across different API versions.

Copilot reviewed 13 out of 13 changed files in this pull request and generated no comments.

[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

> [email protected] 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"


> [email protected] serve
> docusaurus serve --no-open

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

> [email protected] 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:
  158264 links
    1304 destination URLs
    1535 URLs ignored
       0 warnings
       3 errors

 ELIFECYCLE  Command failed with exit code 1.

[noencke]

This seems like a useful tool in certain scenarios. Have you considered an alternative API, where, rather than there being a method on SchemaFactory, you may instead pass in a pre-existing factory when constructing a new factory?

const sfA = new SchemaFactory("A");
const sfB = new SchemaFactory({ parentScope: sfA, scope: "B" });
class C extends sfB.object("C", {}) {}
// C.identifier === "A.B.C"

This is slightly less convenient to invoke, but it also keeps the feature (nested scoping) isolated to precisely where it matters (when defining new scopes) rather than having it be something that pops up in autocomplete every time you type sf.. @Josmithr , curious for your thoughts as well when you have time.

Also, is there a reason this is being introduced on SchemaFactory and not SchemaFactoryAlpha?