Are you sure that your uri .... parameters are formed correctly ?

URIs include components and subcomponents that are delimited by characters in the "reserved" set. These characters are called "reserved" because they may (or may not) be defined as delimiters by the generic syntax, by each scheme-specific syntax, or by the implementation-specific syntax of a URI's dereferencing algorithm. If data for a URI component would conflict with a reserved character's purpose as a delimiter [emphasis added], then the conflicting data must be percent-encoded before the URI is formed.

https://www.rfc-editor.org/rfc/rfc3986#section-2.2

I think you have a problem with the "==" in your string. The "sign" is a reserved sub-delim character
... and you need to do the percent-encoding / url-encoding

https://www.rfc-editor.org/rfc/rfc3986#section-2.1

Probably Bruno is not handling / showing the data for this reason not correctly in your first screenshot

I think this is a serious bug and important feature to fix, but it comes with a bunch of design decisions to make. The URL field should probably validate its contents and notify user if the value is not correctly formatted URL - and what @Chibane690 inputs is in fact invalid.

Is bruno supposed to silently try to url encode the value of URL field? What request is actually being sent from this example? What if loading a bru file where the query section does not match url section? Which takes precedence? It would be nice to have an input from maintainers (@helloanoop) on their vision for this, so someone could pick this up.

A UI solution in this particular case would look something like this, I think - but it takes more than that to iron out this issue:
Params to URL converion on the fly

Params from URL converted on the fly (assuming user types in url-encoded format, which is perhaps much to ask from a human).

I downloaded the Postman client to perform the same test, and it worked well. It escaped the quotes but not the "==" when sending the request, rather than during inputting the request.

Here's a screenshot illustrating the request input:

And here's the image during the request emission:

The execution went smoothly without any bugs.