chore(deps): bump the npm_and_yarn group across 3 directories with 2 updates (#1751)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/launchdarkly/js-core/network/alerts).

</details>

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Lockfile-only dependency updates in devDependencies and private
examples; no changes to published SDK APIs or runtime behavior for
consumers.
> 
> **Overview**
> Dependabot bumps **dev/example** dependencies only—no SDK source
changes.
> 
> **Electron** (`packages/sdk/electron`): devDependency `electron` moves
from **^34.5.6** to **^42.4.0** so Jest/tests run against a newer
Electron; the published **peer** range (`>=34.5.6`) is unchanged.
> 
> **Next.js** (Vercel examples): `complete` patches **15.5.14 →
15.5.18**; `route-handler` upgrades **14.2.35 → 15.5.18**, aligning that
sample on Next 15 with the other example.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
72046ca. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Author: dependabot[bot]

packages/sdk/electron/package.json

@@ -58,7 +58,7 @@
   "devDependencies": {
     "@eslint/js": "^9.0.0",
     "@types/jest": "^29.4.0",
-    "electron": "^34.5.6",
+    "electron": "^42.4.0",
     "eslint": "^9.0.0",
     "eslint-import-resolver-typescript": "^4.0.0",
     "eslint-plugin-import-x": "^4.0.0",

packages/sdk/vercel/examples/complete/package.json

@@ -14,7 +14,7 @@
     "@vercel/edge-config": "^1.1.0",
     "launchdarkly-js-client-sdk": "^3.1.3",
     "launchdarkly-react-client-sdk": "^3.0.6",
-    "next": "15.5.14",
+    "next": "15.5.18",
     "react": "18.2.0",
     "react-dom": "18.2.0"
   },

packages/sdk/vercel/examples/route-handler/package.json

@@ -11,7 +11,7 @@
   "dependencies": {
     "@launchdarkly/vercel-server-sdk": "workspace:^",
     "@vercel/edge-config": "^1.1.0",
-    "next": "14.2.35",
+    "next": "15.5.18",
     "react": "^18.2.0",
     "react-dom": "18.2.0"
   },