Support initial values for things based on CommandForm

[einari]

In Arc we have CommandForm and in this repo implementations of it and also implementations of field types.

Look at the new capabilities of Arcs CommandForm and field types: Cratis/Arc#2549
And make sure we support that for our command forms and field types.

---

Dependencies

Depends on

• CommandForm should support being populated at startup Arc#2549 — the CommandForm and field-type capabilities this implements against

Blocks

• Form designer UI StudioIssues#157 — form designer UI

Modeled by Cratis/Screenplay#91 — the form construct whose populate sources this renders.

Part of the screen work — build order and full dependency map: Cratis/Scene#7

[einari]

Fixed in #134. Investigation found every field component here is a thin asCommandFormField wrapper with no logic of its own around initial values, so Arc#2549's new populateFromQuery/populateFromObservableQuery/noInitialValue/initialValue already flow through automatically once resolved to @cratis/arc.react >= 21.16.0 - confirmed against the published package's compiled types, no field code changed. #134 documents the capability with a Components example.

Also found and flagged (not fixed here, out of scope): resolving to any @cratis/arc.react newer than 21.0.2 currently breaks DataTables/DataTableForObservableQuery.tsx's typecheck - a pre-existing, unrelated incompatibility (reproduces identically at 21.15.0, the version immediately before #2549). Worth a dedicated follow-up issue.