Update selenium and electron-chrome selenium plugin for end 2 end tests. Fixes the e2e stuff that fails on GitHub now that electron has changed versions. Added this step to new nodejs upgrade guide doc

Author: bitmold

docs/Upgrading Nodejs.md

@@ -109,7 +109,11 @@ New versions of add/remove command line flags. If you need to make this change u
 ```
 7. Update `electron`
 
-Migrate `packages/desktop/package.json` to an electron version that ships with the new node verison.
+Migrate `packages/desktop/package.json` to an electron version that ships with the new node verison. 
+
+- You can see each major electron release's nodejs [here](https://releases.electronjs.org/release?channel=stable)
+- Pay careful attention to breaking changes within electron releases. APIs can be removed which will make your project fail to build. But also, and more subtly, the behavior of a certain API may change causing Quiet to build and perhaps seem OK, but something is now behaving differently and/or incorrectly.
+- Upgrade the `selenium-webdriver` and the `electron-chromedriver` modules in `packages/e2e-tests/package.json`. `electron-chromedriver` should match the major version of `electron` that you just migrated to in the `desktop` package.
 
 8. Bootsrap
 

packages/e2e-tests/package-lock.json

@@ -37,12 +37,12 @@
     "@quiet/types": "^2.0.2-alpha.1",
     "backend-bundle": "^2.0.1-alpha.4",
     "cross-env": "^5.2.0",
-    "electron-chromedriver": "23.3.13",
+    "electron-chromedriver": "^29",
     "get-port": "^5.1.1",
     "jest": "^29.4.2",
     "luxon": "^3.4.4",
     "path-browserify": "^1.0.1",
-    "selenium-webdriver": "^4.8.0",
+    "selenium-webdriver": "^4.41.0",
     "yargs": "^17.3.1"
   },
   "jest": {