chore(deps): update dependency pino-pretty to v11.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pino-pretty	11.2.1 -> 11.3.0

---

Release Notes

pinojs/pino-pretty (pino-pretty)

v11.3.0

Compare Source

What's Changed

• Bump @​types/node from 20.14.13 to 22.0.0 by @​dependabot in https://github.com/pinojs/pino-pretty/pull/523
• fix: ndjson incorrect url by @​Livour in https://github.com/pinojs/pino-pretty/pull/528
• Bump pino-abstract-transport from 1.2.0 to 2.0.0 by @​dependabot in https://github.com/pinojs/pino-pretty/pull/531
• Bump @​arethetypeswrong/cli from 0.15.4 to 0.16.1 by @​dependabot in https://github.com/pinojs/pino-pretty/pull/530
• Wait for destination to close by @​mcollina in https://github.com/pinojs/pino-pretty/pull/533

New Contributors

• @​Livour made their first contribution in https://github.com/pinojs/pino-pretty/pull/528

Full Changelog: pinojs/pino-pretty@v11.2.2...v11.3.0

v11.2.2

Compare Source

What's Changed

• Type fixes by @​joshkel in https://github.com/pinojs/pino-pretty/pull/522

New Contributors

• @​joshkel made their first contribution in https://github.com/pinojs/pino-pretty/pull/522

Full Changelog: pinojs/pino-pretty@v11.2.1...v11.2.2

---

Configuration

📅 Schedule: Branch creation - "after 5pm every weekday,before 3am every weekday,every weekend" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

• Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
• Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
• If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".