Allow escaping Prompt Variables syntax (e.g. `\{{?value}}`)

[Redflashx12]

I have checked the following:

• I've searched existing issues and found nothing related to my issue.

This feature

• blocks me from using Bruno
• would improve my quality of life in Bruno
• is something I've never seen an API client do before

Describe the feature you want to add, and how it would change your usage of Bruno

My team uses a specific syntax for downstream templating that directly conflicts with Bruno's Prompt Variables feature.

We send payloads containing strings like {{?value}}.
Since Bruno v2.15, the application parses the ? inside the curly braces as a trigger to halt execution and ask the user for prompt input as mentioned in your documentation here. This prevents us from sending the string literally, as it demands a value before the request can proceed.

Describe the solution you'd like
Ideally, I need a way to be able to escape this sequence so Bruno ignores it during parsing but sends it literally in the request body/URL.

Ideally, strict support for backslash escaping:

• Input in Bruno: \{{?tables_field}}
• Sent to Server: {{?tables_field}} (Bruno ignores the prompt trigger)

Describe alternatives you've considered
I am currently forced to use a verbose workaround to "hide" the question mark from the Bruno parser using variable composition:

1. Created a collection variable start_var with value {{.
2. Created a collection variable end_var with value }}.
3. I construct the payload as {{start_prompt}}?value{{end_prompt}}.

This works, but it requires refactoring all our existing requests and makes the request body difficult to read and maintain, and it's honestly also pretty ugly.

Alternatively, I always have to copy and paste the literal "{{?value}}" value into the prompt variable which is even more annoying.

I'd really appreciate it if you could add escaping to prompt variables as well. I tried escaping it on Bruno 3.0.2 like how it should work with normal variables already, e.g. \{{?value}}, and it does not work with prompt variables.

Mockups or Images of the feature

No response