Fix database column input normalization

[abnegate]

What changed

• normalize database-reader Utopia\Database\Document column records at the existing Appwrite source boundary
• preserve the existing array path and column type, format, and size resolution
• add a focused regression test using a real database document

Verification

• red before fix: focused regression failed with TypeError: Column::resolve(): Argument #1 ($column) must be of type array, Utopia\Database\Document given
• green after fix: focused regression passed with 1 test and 2 assertions
• composer format
• composer lint
• composer check
• isolated CI-equivalent Compose suite: 106 tests, 543 assertions

The host-only full test command cannot run the eight NHost/Supabase E2E cases without their database services; the isolated Compose run supplied those services and passed the complete suite.

[greptile-apps]

Greptile Summary

The PR normalizes database-reader column documents into arrays at the existing Appwrite source boundary while preserving the established column resolution logic.

• Converts Utopia\Database\Document column records using getArrayCopy() before resolution.
• Adds a focused regression test confirming string column type and size are preserved.

Confidence Score: 5/5

The PR appears safe to merge with no actionable defects identified.

The normalization occurs before the existing column resolution path, preserves array inputs unchanged, and the regression test directly covers the database-document failure being fixed.

Important Files Changed

Filename	Overview
src/Migration/Sources/Appwrite.php	Adds narrowly scoped normalization for database-reader Document values before the existing array-based column resolver.
tests/Migration/Unit/Sources/AppwriteColumnTest.php	Adds a regression test using a real database document and verifies the resolved string class and size.

_{Reviews (1): Last reviewed commit: "(fix): normalize database column input" | Re-trigger Greptile}