chore(deps): update dependency next to v15.1.2 [security] (#6784)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [next](https://nextjs.org)
([source](https://redirect.github.com/vercel/next.js)) | [`15.1.0` ->
`15.1.2`](https://renovatebot.com/diffs/npm/next/15.1.0/15.1.2) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/next/15.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/next/15.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/next/15.1.0/15.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/next/15.1.0/15.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

### GitHub Vulnerability Alerts

####
[CVE-2024-56332](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-7m27-7ghc-44w9)

### Impact
A Denial of Service (DoS) attack allows attackers to construct requests
that leaves requests to Server Actions hanging until the hosting
provider cancels the function execution.

_Note: Next.js server is idle during that time and only keeps the
connection open. CPU and memory footprint are low during that time._

Deployments without any protection against long running Server Action
invocations are especially vulnerable. Hosting providers like Vercel or
Netlify set a default maximum duration on function execution to reduce
the risk of excessive billing.

This is the same issue as if the incoming HTTP request has an invalid
`Content-Length` header or never closes. If the host has no other
mitigations to those then this vulnerability is novel.

This vulnerability affects only Next.js deployments using Server
Actions.

### Patches

This vulnerability was resolved in Next.js 14.2.21, 15.1.2, and 13.5.8.
We recommend that users upgrade to a safe version.

### Workarounds

There are no official workarounds for this vulnerability.

### Credits

Thanks to the PackDraw team for responsibly disclosing this
vulnerability.

---

### Release Notes

<details>
<summary>vercel/next.js (next)</summary>

###
[`v15.1.2`](https://redirect.github.com/vercel/next.js/compare/v15.1.1...v15.1.2)

[Compare
Source](https://redirect.github.com/vercel/next.js/compare/v15.1.1...v15.1.2)

###
[`v15.1.1`](https://redirect.github.com/vercel/next.js/compare/v15.1.0...v15.1.1)

[Compare
Source](https://redirect.github.com/vercel/next.js/compare/v15.1.0...v15.1.1)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "" (UTC), Automerge - At any time (no
schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/SAP/ui5-webcomponents-react).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS44NS4wIiwidXBkYXRlZEluVmVyIjoiMzkuODUuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Author: renovate[bot]

examples/nextjs-app/package-lock.json

@@ -17,7 +17,7 @@
     "@types/react-dom": "19.0.2",
     "eslint": "9.17.0",
     "eslint-config-next": "15.1.0",
-    "next": "15.1.0",
+    "next": "15.1.2",
     "react": "19.0.0",
     "react-dom": "19.0.0",
     "typescript": "5.7.2"

examples/nextjs-app/package.json

@@ -17,7 +17,7 @@
     "@types/react-dom": "19.0.2",
     "eslint": "9.17.0",
     "eslint-config-next": "15.1.0",
-    "next": "15.1.0",
+    "next": "15.1.2",
     "react": "19.0.0",
     "react-dom": "19.0.0",
     "typescript": "5.7.2"