Configurable URL Encoding

Related to #592 and #604 Problem Description From day 1, Insomnia has always automatically encoded path and query segments in the URL. The initial reason for this was to preserve compatibility with the legacy version of Insomnia (Chrome App) where the URLs were automatically encoded by the Chrome network layer. For a lot of users, this auto-encoding causes problems and the severity is amplified by the fact that it is actually impossible to send non-encoded special characters. Potential Solutions There are a number of ways this can be solved. Please let me know which one you think is best: • Disable automatic encoding completely (likely too disruptive of a change) - In this scenario, there could be a [Template Tag]( for encoding values explicitly • Add option on each query parameter to enable/disable encoding • Add global workspace-level setting to enable/disable encoding • Have a character whitelist for encoding (would solve 90% of …