chore(deps): update dependency remult to v3.3.16

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
remult (source)	3.3.10 → 3.3.16

---

Release Notes

remult/remult (remult)

v3.3.16

Compare Source

• Added support for default values without an arrow function
• Added type info in the field's function response - used for typing stuff :)

v3.3.15

Compare Source

• Added a Node built-in SQLite data provider (remult/remult-node-sqlite), using the native node:sqlite module (#​1034).
• Thanks to @​linoch512 for their first contribution
• groupBy now ignores orderBy fields that are not part of the group by (previously they were passed through to the database, producing an invalid grouped query on SQL Server / Postgres). The rest api additionally ignores orderBy fields that are not included in the api.

v3.3.14

Compare Source

• Fixed a memory leak related to usage of repo(x,y) with infinite different y

v3.3.13

Compare Source

• Fixed groupBy/aggregate with limit/page but no orderBy emitting OFFSET/FETCH without an ORDER BY, which is invalid on SQL Server. A grouped query now falls back to ordering by the group columns, and a pure aggregate skips paging entirely.
• The query api action no longer leaks the items' paging into the aggregate, so the aggregate summarizes the whole filtered set.

v3.3.12

Compare Source

• Fixed issue with auto increment in ArrayEntityDataProvider where the dbname of the auto increment field was different than the member key

v3.3.11

Compare Source

---

Configuration

📅 Schedule: (in timezone Europe/Paris)

• Branch creation
  • "after 10pm,before 6:00am"
• 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.