fix(type): add number.finite keyword to reject Infinity and NaN

[WolfieLeader]

Summary

Closes #1598

Adds number.finite keyword that rejects NaN, Infinity, and -Infinity. Matches Number.isFinite() semantics.

Implementation follows the number.safe pattern exactly:

• numberAllowsNaN: false on the domain node (rejects NaN)
• min/max bounds at ±Number.MAX_VALUE with custom meta: "a finite number" (rejects ±Infinity with a clear error message)

Using min/max rather than a predicate ensures the constraint is composable (intersects with user bounds), JIT-compiled, introspectable, and compatible with the fast-check arbitrary generator.

Error messages:

• Infinity → "must be a finite number (was Infinity)"
• -Infinity → "must be a finite number (was -Infinity)"
• NaN → "must be a number (was NaN)" (domain-level rejection)

Test plan

• Finite numbers accepted (integers, floats, zero, ±MAX_VALUE boundary)
• ±Infinity rejected with descriptive error
• NaN rejected at domain level
• pnpm prChecks passes (format, lint, typecheck, full test suite)

[pullfrog]

Clean implementation that mirrors the number.safe pattern. One required change: allConfig.ts must be regenerated to include "number.finite", otherwise the testAllConfig integration test will fail (pnpm testRepo → pnpm testIntegration → pnpm testAllConfig).

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ pullfrog.com ｜ 𝕏}

[pullfrog]

allConfig.ts is a checked-in generated file that the testAllConfig integration test uses to verify every keyword has a "configured" description. It currently does not include "number.finite", so the test will fail.

Run the generator to update it:

pnpm tsx ark/type/__tests__/integration/generateAllConfig.ts