fix: ensure NumberField validation displays correct errors in React 19

[chirokas]

Closes #6684

Since the change event (which triggers commitValidation) occurs before the blur event (which triggers commit), numberValue remains in its previous state in the update scheduled by commitValidation.

As for why this works as expected in React 18 but not in React 19, I suspect it's related to the refactoring of the React Reconciler.
https://stackblitz.com/edit/vitejs-vite-qsexo8nh?file=README.md

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

react-spectrum/packages/@react-spectrum/numberfield/test/NumberField.test.js

Line 2399 in a7b1a28

expect(input).not.toHaveAttribute('aria-describedby');

Doesn't look like we can test in React Testing Library.

🧢 Your Project:

[snowystinger]

Looks like the right change, tested in MacOS Chrome. I think we'll need to do this in useColorField as well, https://github.com/adobe/react-spectrum/blob/main/packages/%40react-aria/color/src/useColorField.ts#L127
Would you like to handle that in this PR?

[devongovett]

Aren't there some cases where the native change event won't fire? I think it doesn't fire when there are programmatic value changes while the field is focused, and then the user blurs. Here's an example: https://stackblitz.com/edit/vitejs-vite-clzjwygv?file=src%2FApp.tsx&terminal=dev. If you focus the input, and then click the change button, then click outside, no change event is fired.

I think maybe we could fix this by calling validation.commitValidation() in NumberFieldState's commit function?