fix: commit ColorField value on Enter, matching NumberField behavior (Fixes #10445)

[waterWang]

Summary

Pressing Enter in a ColorField now commits the typed value, matching the behavior of NumberField. Previously, typing a hex value and pressing Enter would silently retain the input display but not commit it to the color state — the value was only flushed on blur. If the user then closed a ColorPicker popover with Escape, the typed value was silently discarded and the previous color restored.

Implementation

Mirrors the useNumberField Enter handling pattern (useKeyboard with flushSync(() => commit())):

• Added flushSync import from react-dom
• Added useKeyboard import from ../interactions/useKeyboard
• Added onKeyDown and onKeyUp to props destructuring
• Added useKeyboard hook with an Enter shortcut that calls flushSync(() => commit())
• Merged keyboardProps first in the mergeProps chain so shortcuts run before other handlers

Related

• Fixes ColorField: typed value is not committed on Enter and silently discarded on Escape dismissal #10445
• Sibling fix to ColorPicker's color field doesn't commit its value if the popover is dismissed via outside click #9748 / fix: Make ColorPicker properly commit its new value upon clicking outside the dialog #9768 (the pointer-dismissal path was already fixed; this addresses the keyboard Enter/Escape path that React does not fire blur on unmount for)

Test plan

• Type a hex value into a ColorField and press Enter — value should be committed immediately
• Type a hex value and press Escape — should NOT commit (cancel-on-Escape is conventional)
• Tab out of the field — value should commit on blur (existing behavior, unchanged)
• All existing tests should pass

[snowystinger]

Thanks for the speedy PR
Please add tests, there are probably some in RAC NumberField that you can base them on.

[snowystinger]

I suspect we'll need the commitValidation as well so that it gets marked invalid before an implicit form submission