Relax JSON strictness in the Dataclip editor

Problem

The Dataclip editor currently requires strict JSON formatting, which slows down
quick edits and prototyping. Small syntax variations that are valid in JavaScript
(like unquoted keys or trailing commas) cause unnecessary friction.

Proposed Solution

Allow JavaScript object syntax in the editor:

• Unquoted keys
• Trailing commas
• Single quotes
• Comments

Example of what should be supported:

{
  name: 'John',
  age: 30,
  tags: ['dev', 'qa'],  // trailing comma OK
}

Instead of requiring:

{
  "name": "John",
  "age": 30,
  "tags": ["dev", "qa"]
}

Impact

Streamlines developer experience during rapid testing and iteration.

User Feedback

"I'd LOVE IT if it would let you write JavaScript objects, not pure JSON."
"There's no reason for us to be strict."

Start by locating the Dataclip editor and the code that parses or validates its input. Check how editor values are converted before saving or execution, then identify existing tests for invalid JSON or Dataclip editing. Done means the editor accepts the listed JavaScript object syntax while preserving the expected Dataclip behavior.