fix(form): move FormItem rule registration out of render phase

[leno23]

Motivation

• Prevent state mutations during render by moving rule registration out of the render path and into an effect so setting field rules no longer happens while React is rendering.
• Ensure field validation rules are only re-registered when relevant inputs change (name, rules, context or declared dependencies) instead of on every render.
• Replace the hacky void ctx.values[dep] read-to-trigger approach with an explicit derived dependency tracking so effect dependencies are predictable.

Description

• Modified packages/ui/src/components/form/Form.tsx to import useEffect and moved ctx.setFieldRules(name, rules) from the render body into a useEffect that depends on ctx, name, rules, and a derived dependencyValues.
• Replaced dependencies.forEach(dep => void ctx.values[dep]) with const dependencyValues = useMemo(() => dependencies.map(dep => ctx.values[dep]), [dependencies, ctx.values]) and included it in the effect dependencies.
• This change avoids writing to rulesMap during render and re-registers rules only when the context, name, rules, or actual dependency-derived values change.

Testing

• Ran lint with npm run lint:ui, which completed successfully.
• Ran TypeScript checks with npm run typecheck:ui, which completed successfully.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 29b59e05d2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Register rules synchronously before submit can run

Moving ctx.setFieldRules(name, rules) into useEffect delays rule registration until after the first paint, so validate() can run with an empty rulesMap during the initial mount cycle. This is observable when a consumer submits imperatively on mount (for example from a parent useLayoutEffect/ref call): the first submit bypasses required/pattern checks and can call onSubmit with invalid values, whereas the previous render-phase registration made rules available immediately.

Useful? React with 👍 / 👎.