feat(tree): Update experimental Table Schema APIs to support adding additional properties to Column/Row Schema

[Josmithr]

This PR also decouples Row and Column schema. Row previously took schema-specific Column as input so it could offer APIs that took in Column nodes. These have been replaced with 2 overloads each: 1 that takes an ID (resolving an existing TODO) and one that takes in an IColumn.

Notes:

• Props schema are currently taken in the form of a node schema (ImplicitAllowedTypes). Preferably, they would be a field schema (ImplicitFieldSchema) so that users could make the property optional. I encountered some issues where TypeScript was generating invalid .d.ts files when I tried this previously. I will continue investigating and make this change in a subsequent PR.
• Props schema are currently required. I will make them optional in a future PR. For now, if props are not desired, the user can specify SchemaFactory.null.

[Copilot]

Pull Request Overview

This PR updates the experimental Table Schema APIs to support additional properties for Column and Row schemas by introducing new props schemas and updating the tests and internal type signatures accordingly. Key changes include:

• Introducing ColumnProps and RowProps classes for schema definitions.
• Updating the createColumn, createRow, and createTable implementations and tests to require and handle a new “props” field.
• Adjusting tests to consistently include a props object when creating schema instances.

Reviewed Changes

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

File	Description
packages/dds/tree/src/test/tableSchema.spec.ts	Updates to test cases to include props for columns and rows.
packages/dds/tree/src/tableSchema.ts	Adjustments to schema creation functions and type signatures to support props.
examples/utils/import-testing/src/test/importer.spec.ts	Updates to integration tests to utilize the new props-based API.

Comments suppressed due to low confidence (2)

packages/dds/tree/src/test/tableSchema.spec.ts:77

• Consider adding tests for cases where the props field is omitted to ensure the schema behaves as expected when props are not provided, which will help ensure backward compatibility.

treeView.initialize(new Table({

packages/dds/tree/src/tableSchema.ts:470

• Add inline documentation clarifying that using 'inputSchemaFactory.null' as the default for props is a temporary workaround, and consider extracting this logic into a helper function to improve readability.

const column = columnSchema ?? createColumn(inputSchemaFactory, inputSchemaFactory.null);

[Josmithr]

We discovered that the satisfies clause here was actually resulting in different (and incorrect) typing to be applied to rowFields. This appears to be a TypeScript bug. But since this extra check isn't really necessary for type-safety in this function, it can be safely removed.