fix(deps): update mikro-orm monorepo to v5.9.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@mikro-orm/core (source)	5.9.7 -> 5.9.8
@mikro-orm/mongodb (source)	5.9.7 -> 5.9.8
@mikro-orm/mysql (source)	5.9.7 -> 5.9.8

---

Release Notes

mikro-orm/mikro-orm (@​mikro-orm/core)

v5.9.8

Compare Source

Bug Fixes

• core: do not mutate data provided to em.upsert/Many (5acb4eb), closes #​5136
• core: ensure em.insertMany returns array of PKs for a single item too (#​5180) (b9a55e5), closes #​5179
• core: process upsert data to allow using entity instances in place of relations (42e3c5e), closes #​5165
• mongo: ensure assign on object properties won't ignore changes (bd22d7c), closes #​5158
• postgres: parse timestamp dates less than year 1000 (#​5071) (63eb5c5)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 these updates again.

---

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

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: sample/011-mirkoorm-app/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/[email protected]
npm error Found: [email protected]
npm error node_modules/reflect-metadata
npm error   reflect-metadata@"0.2.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm error node_modules/@nestjs/common
npm error   @nestjs/common@"10.3.1" from the root project
npm error   peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @mikro-orm/[email protected]
npm error   node_modules/@mikro-orm/nestjs
npm error     @mikro-orm/nestjs@"5.2.3" from the root project
npm error     1 more (@nestjs/terminus)
npm error   4 more (@nestjs/core, @nestjs/platform-express, ...)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/reflect-metadata
npm error   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm error   node_modules/@nestjs/common
npm error     @nestjs/common@"10.3.1" from the root project
npm error     peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @mikro-orm/[email protected]
npm error     node_modules/@mikro-orm/nestjs
npm error       @mikro-orm/nestjs@"5.2.3" from the root project
npm error       1 more (@nestjs/terminus)
npm error     4 more (@nestjs/core, @nestjs/platform-express, ...)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-08T23_19_06_184Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-08T23_19_06_184Z-debug-0.log

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @mikro-orm/[email protected]
npm ERR!     node_modules/@mikro-orm/nestjs
npm ERR!       dev @mikro-orm/nestjs@"5.2.3" from the root project
npm ERR!     11 more (@nestjs/axios, @nestjs/core, @nestjs/mapped-types, ...)
npm ERR!   7 more (@nestjs/core, @nestjs/mapped-types, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/sequelize
npm ERR!   dev @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/sequelize
npm ERR!     dev @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-12-08T23_19_34_301Z-debug-0.log