(feat): add Schema\Order for index column directions

[abnegate]

Why

Index definitions already use IndexType. Column direction was still 'ASC' / 'DESC' (or Database::ORDER_* at call sites). That is the same class of magic string IndexType removed.

OrderDirection stays on the query AST because it includes RANDOM, which is not a valid index column order.

What

• Utopia\Query\Schema\Order with Asc / Desc
• Schema index DDL validates orders through Order::tryFrom()

Not verified

• Downstream call sites in database / migration / Appwrite (follow-up on those PRs)

[greptile-apps]

Greptile Summary

Adds a schema-specific Order enum for index column directions while preserving the existing validation behavior.

• Defines Order::Asc and Order::Desc.
• Uses Order::tryFrom() when validating SQL index column directions.
• Adds unit coverage for the enum values.

Confidence Score: 5/5

The PR appears safe to merge with no actionable correctness or security issues identified.

The new enum is compatible with the package’s supported runtime and preserves the existing case-insensitive ASC/DESC validation semantics for all reachable string inputs.

Important Files Changed

Filename	Overview
src/Query/Schema.php	Replaces explicit ASC/DESC comparisons with equivalent validation through the new schema enum.
src/Query/Schema/Order.php	Introduces a backed enum containing the two valid index column directions.
tests/Query/Schema/OrderTest.php	Verifies that the enum cases retain the expected uppercase SQL values.

_{Reviews (1): Last reviewed commit: "(feat): add Schema\Order for index colum..." | Re-trigger Greptile}

[github-actions]

📊 Coverage

Metric	PR	Baseline	Δ
Lines	91.88% (7559/8227)	91.88%	+0.00%
Methods	83.89% (1114/1328)	83.89%	+0.00%
Classes	65.16% (144/221)	65.45%	-0.30%

Full per-file breakdown in the job summary.