Name collisions from structurally named schema now error

[CraigMacomber]

Description

See changeset.

Breaking Changes

Some malformed schema which previously behaved incorrectly will now err.

Reviewer Guidance

The review process is outlined on this wiki page.

[Copilot]

Pull Request Overview

This PR enforces unique structurally named schemas by comparing input and existing definitions and throws a UsageError on mismatch.

• Introduces a shared helper (getStructuralType) in schemaFactory.ts to validate and cache structural types for arrays and maps.
• Adds unit tests (schemaFactory.spec.ts) for single- and multi-type collisions to ensure errors are thrown on mismatches.
• Adds a changelog entry (.changeset/social-bears-deny.md) documenting the breaking change.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
packages/dds/tree/src/test/simple-tree/api/schemaFactory.spec.ts	Adds tests for single and multi-type schema collisions.
packages/dds/tree/src/simple-tree/api/schemaFactory.ts	Implements getStructuralType to detect and error on collisions.
.changeset/social-bears-deny.md	Documents the new error behavior for structurally named schemas.

Comments suppressed due to low confidence (1)

packages/dds/tree/src/simple-tree/api/schemaFactory.ts:994

• [nitpick] The variable name same is generic; consider renaming it to something more descriptive like typesMatch or schemasEqual to clarify its role in the comparison.

const same = compareSets({ a: inputTypes, b: outputTypes });