chore(deps): update dependency mongoose to v7.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
mongoose (source)	7.2.3 -> 7.3.0

---

Release Notes

Automattic/mongoose

v7.3.0

Compare Source

==================

• feat: upgrade mongodb -> 5.6.0 #​13455 lorand-horvath
• feat(aggregate): add Aggregate.prototype.finally() to be consistent with Promise API for TypeScript #​13509
• feat(schema): support selecting subset of fields to apply optimistic concurrency to #​13506 #​10591
• feat(model): add ordered option to Model.create() #​13472 #​4038
• feat(schema): consistently add .get() function to all SchemaType classes
• feat(populate): pass virtual to match function to allow merging match options #​13477 #​12443
• types: allow overwriting Paths in select() to tell TypeScript which fields are projected #​13478 #​13224
• types(schema): add validateModifiedOnly as schema option #​13503 #​10153
• docs: add note about validateModifiedOnly as a schema option #​13503 #​10153
• docs(migrating_to_7): update migrating_to_7.md to include Model.countDocuments #​13508 Climax777
• docs(further_reading): remove style for "img" hasezoey

v7.2.4

Compare Source

==================

• fix(query): handle non-string discriminator key values in query #​13496 #​13492

---

Configuration

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

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[humanscape-james]

changing schema.factory.ts > line 16 (createForClass)

• from return new mongoose.Schema<TClass>(

• to return new mongoose.Schema<TClass, any, any, any, any, any>(

makes build and test(npm run test:e2e) success...

but I am not sure if this is enough for mongoose's breaking changes from v6 to v7 🤔

[cwoebker]

@kamilmysliwiec Do you have a timeline in mind on when mongoose v7 support might land? Thanks for all of your work!