Form Field Visibility Conditions

Form definitions now include each field's visibility condition, so integrations that render an Ashby form elsewhere can show, hide and require fields the same way Ashby does. This feature is in beta and may not be available for all organizations. Applies everywhere a form definition is returned:
- Forms to be filled out: offer.start, offer.info, offer.create, offer.update, offer.setStatus, offer.setDecidedAt, offer.startApprovalProcess, offer.approve, offer.reject, jobPosting.info, jobPosting.create, jobPosting.update, jobPosting.setStatus, jobPosting.updateCompensation, jobPosting.updateCompensationSettings, referralForm.info, surveyFormDefinition.info, surveyFormDefinition.list, feedbackFormDefinition.info, feedbackFormDefinition.list and interviewBriefing.info.
- Submitted forms, whose definition accompanies the submitted values: applicationForm.submit, application.info (with expand: ["applicationFormSubmissions"]), applicationFeedback.list, applicationFeedback.submit, referral.list, surveySubmission.create and surveySubmission.list.
- Webhooks whose payload carries one of these objects: the offer, candidate hire and survey submit webhooks.
- The .list endpoints above return it only when includeVisibilityConditions: true is passed.
A condition keeps the rule's two levels: and, or and not combine conditions, and each field node holds the query on that field's submitted value, compared with isEmpty, isNotEmpty, equals, idEquals, contains, startsWith, endsWith, greaterThan, lessThan, between or intersects.
Conditions a caller cannot evaluate are marked as unknown rather than omitted, with a reason. A rule on data outside the form (externalData) includes the rule itself where it can: query for a field of a linked record, condition for a subquery on one. Other externalData nodes carry only the fieldPath. A rule on a field no longer on the form is unavailable, and anything else the encoding cannot express is unsupported. Rules on date ranges currently encode as unknown too.