Fix script deletion during execution on desktop

This commit fixes an issue seen on certain Windows environments (Windows
10 22H2 and 11 23H2 Pro Azure VMs) where scripts were being deleted
during execution due to temporary directory usage. To resolve this,
scripts are now stored in a persistent directory, enhancing reliability
for long-running scripts and improving auditability along with
troubleshooting.

Key changes:

- Move script execution logic to the `main` process from `preloader` to
  utilize Electron's `app.getPath`.
- Improve runtime environment detection for non-browser environments to
  allow its usage in Electron main process.
- Introduce a secure module to expose IPC channels from the main process
  to the renderer via the preloader process.

Supporting refactorings include:

- Simplify `CodeRunner` interface by removing the `tempScriptFolderName`
  parameter.
- Rename `NodeSystemOperations` to `NodeElectronSystemOperations` as it
  now wraps electron APIs too, and convert it to class for simplicity.
- Rename `TemporaryFileCodeRunner` to `ScriptFileCodeRunner` to reflect
  its new functinoality.
- Rename `SystemOperations` folder to `System` for simplicity.
- Rename `HostRuntimeEnvironment` to `BrowserRuntimeEnvironment` for
  clarity.
- Refactor main Electron process configuration to align with latest
  Electron documentation/recommendations.
- Refactor unit tests `BrowserRuntimeEnvironment` to simplify singleton
  workaround.
- Use alias imports like `electron/main` and `electron/common` for
  better clarity.

docs/desktop-vs-web-features.md

@@ -50,5 +50,12 @@ Log file locations vary by operating system:
 
 ### Script execution
 
-Direct execution of scripts is possible in the desktop version, offering a more integrated experience.
-This functionality is not present in the web version due to browser limitations.
+The desktop version of privacy.sexy enables direct script execution, providing a seamless and integrated experience.
+This direct execution capability isn't available in the web version due to inherent browser restrictions.
+
+For enhanced auditability and easier troubleshooting, the desktop version keeps a record of executed scripts in designated directories.
+These locations vary based on the operating system:
+
+- macOS: `$HOME/Library/Application Support/privacy.sexy/runs`
+- Linux: `$HOME/.config/privacy.sexy/runs`
+- Windows: `%APPDATA%\privacy.sexy\runs`