[Snyk] Security upgrade electron from 29.2.0 to 29.3.1

[melvin-bot[bot]]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

#### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - package.json

⚠️ Warning

``` Failed to update the package-lock.json, please update manually before merging. ```

#### Vulnerabilities that will be fixed ##### With an upgrade: Severity | Issue | Breaking Change | Exploit Maturity :-------------------------:|:-------------------------|:-------------------------|:-------------------------  | Use After Free
[SNYK-JS-ELECTRON-6613084](https://snyk.io/vuln/SNYK-JS-ELECTRON-6613084) | No | No Known Exploit  | Heap-based Buffer Overflow
[SNYK-JS-ELECTRON-6613085](https://snyk.io/vuln/SNYK-JS-ELECTRON-6613085) | No | No Known Exploit  | Out-of-bounds Write
[SNYK-JS-ELECTRON-6613086](https://snyk.io/vuln/SNYK-JS-ELECTRON-6613086) | No | No Known Exploit Check the changes in this PR to ensure they won't cause issues with your project. ------------ **Note:** *You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.* For more information: 🧐 [View latest project report](https://app.snyk.io/org/expensify/project/a75415c0-01a0-4906-abb8-070d86e05d58?utm_source=github&utm_medium=referral&page=fix-pr) 🛠 [Adjust project settings](https://app.snyk.io/org/expensify/project/a75415c0-01a0-4906-abb8-070d86e05d58?utm_source=github&utm_medium=referral&page=fix-pr/settings) 📚 [Read more about Snyk's upgrade and patch logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities) [//]: # (snyk:metadata:{"prId":"8d663203-757c-4b5d-9a5d-e4203afc274e","prPublicId":"8d663203-757c-4b5d-9a5d-e4203afc274e","dependencies":[{"name":"electron","from":"29.2.0","to":"29.3.1"}],"packageManager":"npm","projectPublicId":"a75415c0-01a0-4906-abb8-070d86e05d58","projectUrl":"https://app.snyk.io/org/expensify/project/a75415c0-01a0-4906-abb8-070d86e05d58?utm_source=github&utm_medium=referral&page=fix-pr","type":"auto","patch":[],"vulns":["SNYK-JS-ELECTRON-6613084","SNYK-JS-ELECTRON-6613085","SNYK-JS-ELECTRON-6613086"],"upgrade":["SNYK-JS-ELECTRON-6613084","SNYK-JS-ELECTRON-6613085","SNYK-JS-ELECTRON-6613086"],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","pr-warning-shown"],"priorityScoreList":[null,null,null],"remediationStrategy":"vuln"}) --- **Learn how to fix vulnerabilities with free interactive lessons:** 🦉 [Use After Free](https://learn.snyk.io/lesson/use-after-free/?loc=fix-pr)

[melvin-bot[bot]]

This is a Snyk issue. Snyk is a tool that automatically tracks our repositories' dependencies and reports associated security vulnerabilities. It also automatically create PRs to fix these vulnerabilities.

    C+: Please follow these steps to test the linked PR before running through the reviewer checklist:
    - [ ] The first step is to understand the PR: what dependency is it upgrading, for which vulnerability, how it impacts our product & end users.
    - [ ] If the issue is not worth fixing, please add your reasoning in the issue and have the internal engineer review it.
    - [ ] Check the change log (which should be included in the PR description) to see all changes. We want to identify any breaking changes. If it is a minor version bump, it's unlikely that there are any breaking changes.
    - [ ] Test our feature(s) that make use of this package. If it does not work, we should understand what broke it. It is also a good idea to check our main flows to make sure they are not broken that you can add in the checklist screenshots/videos.

[melvin-bot[bot]]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @rojiphil (Internal)

[melvin-bot[bot]]

This issue has not been updated in over 15 days. @rojiphil eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!