Order results when using pagination

[c0c0n3]

Describe the bug It looks like result sets aren't ordered when using pagination params, e.g.

• https://github.com/orchestracities/anubis/blob/master/anubis-management-api/anubis/tenants/operations.py#L27

Without order, pagination will be inconsistent, especially when you have lots of rows in the underlying DB table. For example two pages (as determined by the offset and limit params) may wind up having some rows in common:

table: [r1, r2, ..., r100]

offset = 0 && limit = 3   ~~~> [r1, r2, r3]
offset = 3 && limit = 3   ~~~> [r2, r3, r4]

To Reproduce N/A

Expected behavior All queries involving pagination should also have an order by clause.

Additional context See e.g.

• https://www.postgresql.org/docs/current/queries-limit.html

Thus, using different LIMIT/OFFSET values to select different subsets of a query result will give inconsistent results unless you enforce a predictable result ordering with ORDER BY