chore(deps): update dependency yaml to v2.8.3 [security] (#250)

This PR contains the following updates:

| Package | Type | Update | Change | OpenSSF |
|---|---|---|---|---|
| [yaml](https://eemeli.org/yaml/)
([source](https://redirect.github.com/eemeli/yaml)) | dependencies |
patch | [`2.8.2` →
`2.8.3`](https://renovatebot.com/diffs/npm/yaml/2.8.2/2.8.3) |
[![OpenSSF
Scorecard](https://api.securityscorecards.dev/projects/github.com/eemeli/yaml/badge)](https://securityscorecards.dev/viewer/?uri=github.com/eemeli/yaml)
|

### GitHub Vulnerability Alerts

####
[CVE-2026-33532](https://redirect.github.com/eemeli/yaml/security/advisories/GHSA-48c2-rrv3-qjmp)

Parsing a YAML document with `yaml` may throw a RangeError due to a
stack overflow.

The node resolution/composition phase uses recursive function calls
without a depth bound. An attacker who can supply YAML for parsing can
trigger a `RangeError: Maximum call stack size exceeded` with a small
payload (~2–10 KB). The `RangeError` is not a `YAMLParseError`, so
applications that only catch YAML-specific errors will encounter an
unexpected exception type. Depending on the host application's exception
handling, this can fail requests or terminate the Node.js process.

Flow sequences allow deep nesting with minimal bytes (2 bytes per level:
one `[` and one `]`). On the default Node.js stack, approximately
1,000–5,000 levels of nesting (2–10 KB input) exhaust the call stack.
The exact threshold is environment-dependent (Node.js version, stack
size, call stack depth at invocation).

Note: the library's `Parser` (CST phase) uses a stack-based iterative
approach and is not affected. Only the compose/resolve phase uses actual
call-stack recursion.

All three public parsing APIs are affected: `YAML.parse()`,
`YAML.parseDocument()`, and `YAML.parseAllDocuments()`.

### PoC

```javascript
const YAML = require('yaml');

// ~10 KB payload: 5000 levels of nested flow sequences
const payload = '['.repeat(5000) + '1' + ']'.repeat(5000);

try {
  YAML.parse(payload);
} catch (e) {
  console.log(e.constructor.name); // RangeError (NOT YAMLParseError)
  console.log(e.message);          // Maximum call stack size exceeded
}
```

Test environment: Node.js v24.12.0, macOS darwin arm64

| Version | Nesting Depth | Input Size | Result |
|---|---|---|---|
| 1.0.0 | 5,000 | 10,001 B | RangeError |
| 1.10.2 | 5,000 | 10,001 B | RangeError |
| 2.0.0 | 5,000 | 10,001 B | RangeError |
| 2.8.2 | 5,000 | 10,001 B | RangeError |
| 2.8.3 | 5,000 | 10,001 B | YAMLParseError |

Depth threshold on yaml 2.8.2:

| Nesting Depth | Input Size | Result |
|---|---|---|
| 500 | 1,001 B | Parses successfully |
| 1,000 | 2,001 B | RangeError (threshold varies by stack size) |
| 5,000 | 10,001 B | RangeError |

---

### Release Notes

<details>
<summary>eemeli/yaml (yaml)</summary>

###
[`v2.8.3`](https://redirect.github.com/eemeli/yaml/compare/v2.8.2...v2.8.3)

[Compare
Source](https://redirect.github.com/eemeli/yaml/compare/v2.8.2...v2.8.3)

</details>

---

### Configuration

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

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, 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/settlemint/network-bootstrapper).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My45MS41IiwidXBkYXRlZEluVmVyIjoiNDMuOTEuNSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->

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

Author: renovate[bot]

bun.lock

@@ -45,7 +45,7 @@
     "lefthook": "2.1.5",
     "ox": "0.14.10",
     "viem": "2.47.10",
-    "yaml": "2.8.2",
+    "yaml": "2.8.3",
     "zod": "4.3.6"
   }
 }