* ~ only prefill `Bearer` as token prefix only when the oauth2 is selected as the auth type for the first time
~ check if tokenPrefix is present before adding a space before the access_token value in the header
* review comment fixes
---------
Co-authored-by: lohit <lohit@usebruno.com>
* fix: update qs.stringify to use repeat array format for url serialization
* fix(cli): update qs.stringify to use repeat array format for url serialization
* feat(tests): add URL serialization test case for Duplicate Keys
* feat(cli): refactor formUrlEncoded handling to use buildFormUrlEncodedPayload function
* fix(cli): standardize quotes in qs.stringify for form-urlencoded data
* fix(electron): standardize quotes in qs.stringify for form-urlencoded data
Fixed a bug causing secrets to appear as null instead of an empty value.
rm isValidValue and directly handle it in encryptString and `decryptString` function
- Trace will capture snapshots now
- Added ability to add init Electron user-data, preferences and other
app settings.
- Improved test Fixtures
- Use tempdir for Electron user-data
- Ability to reuse app instance for a given init user-data by placing
them in a folder(`pageWithUserData` Fixture)
- Ability to create tests with fresh user-data(`newPage` Fixture)
- Improved logging
- Improved the env vars to customize the Electron user-data-path
URI-encoding the _username_ and _password_ before creating the proxy URI
which then gets passed to `HttpsProxyAgent` and `HttpProxyAgent`
respectively.
If `ELECTRON_APP_NAME` env-variable is present and its development mode,
then the `appName` and `userData` path is modified accordingly.
e.g.
```sh
ELECTRON_APP_NAME=bruno-dev npm run dev:electron
```
Note: This doesn't change the name of the window or the names in lot of
other places, only the name used by Electron internally.
By default Axios will set the Content-Type for POST/PUT/PATCH requests
to "application/x-www-form-urlencoded" if the Content-Type header is not
specified.
This explicitly sets the content type to "false" when there the body
mode is set to "none", and the user has not set an explicit content type
themselves. Setting the content type to false directs Axios not to send
a Content-Type header.
