Fix crash when an if.required field has a json-logic validation

[thiamsantos]

Summary

Fixes a crash when a form field appears in a conditional's required list and also has a json-logic validation.

Why

createHeadlessForm threw required validation "" doesn't exist for a valid schema, so the form could not be built or validated. The named validation was defined at the schema root the whole time; the conditional's type-error check could not see it. This blocked any schema that pairs if.required with x-jsf-logic-validations on the same field.

How

forward jsonLogicContext (already in scope) and a path into that validateSchema call.

---

Note

Low Risk
Single-argument change on an internal conditional type-check path; behavior is narrowed to schemas that combine if.required with json-logic validations on the same field.

Overview
Fixes a build/validation crash when a field listed in a conditional’s if.required also declares x-jsf-logic-validations. The type-error gate inside evaluateConditional now passes the existing jsonLogicContext (and path) into validateSchema, so json-logic rules resolve from the root schema instead of throwing that a named validation “doesn’t exist.”

Adds a fixture and tests for field_a with both if.required and a_at_least_ten: form creation no longer throws, the then branch still requires field_c alongside logic errors, and the else branch still hides field_c while logic validation runs.

^{Reviewed by Cursor Bugbot for commit a828b20. Bugbot is set up for automated code reviews on this repo. Configure here.}