console: gql api unreachable due to special characters in headers

### Version Information

Server Version:
v2.14.0-cloud.1

### Environment
Cloud

### Screenshot

### What is the current behaviour?
If we are adding special characters to headers in the API tab, the requests doesn’t get sent due to no url encoding, and console responds with an error message

### What is the expected behaviour?
Url encoding of headers should be there, to make network requests reach the server.

### How to reproduce the issue?

1. Open API tab
2. Add a new header with some special characters

### Keywords

Console, cloud, api tab, url encoding

Start by reproducing the issue in the Console API tab with a header containing special characters, then trace how the request is constructed before it reaches the server. The work is done when such headers are URL-encoded and the request succeeds instead of producing the reported error.

Written by the indexing model from the issue text.