Fix: File path fails when used in env vars on Windows [INS-4742]

[filfreire]

Fix

When we do a double-escape of the \ slash on tag-editor.tsx it solves the issue.

It seems before we were sanitizing the tag in different ways, and that didn't work, but it's unclear how it may have worked years ago. For now this change seems to do the trick

Explored some alternatives, but going down the path of JSON.stringify'ing the argument elsewhere, or trying to sanitize it elsewhere, becomes a trap quickly and doesn't fully work.

Investigation details here

Note: dragons 🐉 and spaghetti 🍝 ,

this is failing as far back as 2023. Tried with 10.1.1, 8.5.1 and even 2023.5.8. Found a bug report about it here: #5754

this is a sandworm/Shai-hulud type of issue for spending time

When using File template tags as value for environment variables in the JSON / non-table view of the Environment Editor, the file path gets stored with a bad path on the environment.

• Does not seem to happen when setting the file template tag in the new environment table view editor, it's specific to the JSON view
• Throughout the codebase there's a handful of places where we replace \\\\ to \\
• There's also places where we do the oposite
• By the time we get the values from Env Editor, it's showing up as \\ - which then magically dissappears when attempting to use the Env variable in a request, so a string like C:\\Users\\filipe\\Desktop\\test.txt ends up as C:\UsersfilipeDesktoptest.txt
• In other cases it ends up weirder, particularly when using the Packaged app instead of the local development, where it ends up adding the AppData\Local\insomnia\app-10.2.0 path to the full bad path.
  

Closes INS-4742

Closes #5754

[gatzjames]

Tested on Windows and macOS LGTM