docs: tighten generated helper schemas

[S4Mi]

Summary

• Compose Formaloo logic condition args as either a documented logic argument or a nested condition object, while leaving nested condition internals flexible for recursive and/or trees.
• Preserve the logic helper shape through the MCP filtered OpenAPI build.
• Align curated logic operation/action/argument enums with formz_core backend constants, including documenting disable as backend-accepted but currently no-op/not UI-exposed.
• Add validation coverage for backend-derived logic enums and choice-like bulk_choices as string[] or newline string.

Source audit

• formz_core/formz/logic/utils/constants.py: authoritative logic action, operation, and argument constants.
• formz_core/formz/logic/serializers/v1.py: and/or recursively validate nested OperationSerializer args; operation-specific arg tuple types remain intentionally loose.
• formz_core/formz/logic/utils/analyzer.py: disable has an analyzer branch but currently performs no behavior.
• formz_core/formz/rest/serializers/v5/fields.py: BulkChoicesInputField accepts array labels or newline string.
• frontend-monorepo/apps/dashboard/components/Logic/utils/convertor/getFlatWhen.tsx: frontend documents the missing true recursive NestedCondition type.

Validation

• npm run validate-spec
• npm run validate:mcp-spec

Note: validate:mcp-spec still reports the existing WhatsApp operation-description warnings, but no errors.