fix(sections-editor): reject decimal/exponent input on integer schema fields

[pedrofrxncx]

Found while doing a post-merge sanity check on #5331 (which wired apps/web/ct/tests/widget-dispatch.ct.tsx into CI). That test only asserts the inputmode attribute for number vs integer schema dispatch, so it never caught that NumberField's partial-input regex (apps/web/src/components/sections-editor/fields/number-field.tsx) accepted a decimal point and exponent for BOTH number and integer JSON-schema types.

Failure scenario: any tool/section field with an integer schema (e.g. a quantity, port, or count) routes through schema-form.tsx's case "integer" to the same NumberField as number. A user typing 1.5 or 1e5 into that field has it accepted keystroke-by-keystroke and onChange fires with Number("1.5") === 1.5 — a non-integer value gets persisted into org config with nothing downstream re-validating it against the integer schema.

Fix: extracted the partial-number matcher into fields/partial-number-input.ts as isPartialNumericInput(value, isInteger), with a second regex (^[+-]?\d*$) used when the schema is integer — rejecting . and e outright instead of only filtering on the shared decimal/exponent-permissive pattern. Behavior for number schemas is unchanged (same regex, same acceptance set).

Regression test: apps/web/src/components/sections-editor/fields/partial-number-input.test.ts — asserts integer mode rejects "1.5", "1e5", ".5", etc. while still accepting in-progress typing ("", "-", "42"), and that number mode is unaffected.

Reviewer command: cd apps/web && bun test src/components/sections-editor/fields/partial-number-input.test.ts

Locally ran: bun run fmt, cd apps/web && bunx tsc --noEmit (clean), and the targeted test above (3 pass). Full CI covers the rest (including the ct suite this doesn't touch).

---

Summary by cubic

Rejects decimal and exponent input in integer fields in the sections editor to prevent non-integer values from being saved. Extracted a shared numeric input validator and wired it into NumberField; behavior for number schemas is unchanged.

• Bug Fixes
  • Added isPartialNumericInput in fields/partial-number-input.ts with an integer-safe pattern (no "." or "e").
  • Updated NumberField to use the validator when schema.type === "integer".
  • Added tests to confirm integer mode rejects decimal/exponent while number mode stays permissive.

^{Written for commit 3e66422. Summary will update on new commits.}