fix(web): enable JSON_OBJECT type support in console UI

[tomerqodo]

Benchmark PR from qodo-benchmark#439

[augmentcode]

🤖 Augment PR Summary

Summary: This PR enables editing/support for JSON_OBJECT input variables in the console UI.

Changes:

• Updates the JSON schema placeholder to a full JSON Schema object (type/properties) rather than just a properties map.
• Stores and displays the full json_schema content in the config modal (instead of only .properties).
• Enables the JSON_OBJECT type option for non-basic apps and normalizes empty schemas by removing json_schema from the saved payload.
• Adds confirm-time validation + localized error messages when the schema is invalid JSON or not an object schema.

Technical Notes: The modal now persists json_schema as the raw JSON string and validates schema.type === "object" before saving.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

jsonSchemaStr’s useMemo reads type, but the dependency list only includes tempPayload.json_schema, so the memoized value can become stale if the user switches the input type away from JSON and then back.

_{🤖 Was this useful? React with 👍 or 👎}

[augmentcode]

return True will throw at runtime because True isn’t a defined identifier in JS/TS, which would break JSON schema editing as soon as onChange fires.

_{🤖 Was this useful? React with 👍 or 👎}