Pagination of Messages

[Magnus-Kuhn]

Readiness checklist

• I added/updated tests.
• I ensured that the PR title is good enough for the changelog.
• I labeled the PR.
• I self-reviewed the PR.

Description

A first bare-bones implementation using the existing docdb-database-abstractions pagination without a default or restrictions for the requested pagination.

A bug is that count(query: {}) on lokijs always returns 0, we run into this because the querytranslator translates an undefined query to {}.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files with missing lines	Coverage Δ
...src/extensibility/facades/AppRelationshipFacade.ts	71.79% <100.00%> (+0.54%)	⬆️
...ransport/src/modules/messages/MessageController.ts	88.07% <100.00%> (+0.28%)	⬆️
...ansport/src/modules/sync/SynchronizedCollection.ts	35.24% <100.00%> (ø)
...rt/src/modules/sync/migrations/DeviceMigrations.ts	100.00% <100.00%> (ø)

... and 355 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jkoenig134]

@Magnus-Kuhn why is this a breaking change?

[Magnus-Kuhn]

The total number of messages is returned as well in the use case as {messages: MessageDTO[], messageCount: number}.

[jkoenig134]

The total number of messages is returned as well in the use case as {messages: MessageDTO[], messageCount: number}.

IMO no real reason. We can keep the connector api the same and we can update the App accordingly.