fix: correct invalid JSON in Swagger UI examples for list parameters

[awalker4]

The examples for languages, ocr_languages, and skip_infer_table_types parameters were using invalid JSON syntax (e.g., "[eng]" instead of '["eng"]'). This caused Swagger UI to fail rendering the /general/doc endpoint with the error: "Unexpected token 'e', "[eng]" is not valid JSON"

Changed:

• languages: "[eng]" -> '["eng"]'
• ocr_languages: "[eng]" -> '["eng"]'
• skip_infer_table_types: "['pdf', 'jpg', 'png']" -> '["pdf", "jpg", "png"]'

These parameters use multipart/form-data which requires stringified JSON for array values. The fix uses proper JSON syntax with double quotes, matching the pattern used elsewhere (e.g., extract_image_block_types).

Fixes #537

---

Note

Low Risk
Doc/Swagger example-only updates to form parameter metadata; no runtime logic or request parsing changes.

Overview
Fixes invalid JSON shown in Swagger UI examples for multipart/form-data list parameters in GeneralFormParams.as_form.

Updates the examples strings for languages, ocr_languages, and skip_infer_table_types to use proper JSON array syntax (double-quoted strings), preventing Swagger UI rendering errors for the /general/doc endpoint.

^{Written by Cursor Bugbot for commit f408553. This will update automatically on new commits. Configure here.}