Workspaces API - order by schema fields instead of database fields

[harminius]

Fixes 1. and 3. in https://github.com/MerginMaps/server-private/issues/3154#issuecomment-3778290318

• adds helper to map API field names to DB column names based on Schema
• when invalid order param is passed error is thrown

[coveralls]

Pull Request Test Coverage Report for Build 21283805147

Details

• 48 of 49 (97.96%) changed or added relevant lines in 4 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.04%) to 94.408%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
server/mergin/utils.py	22	23	95.65%

Totals
Change from base Build 21063718610:	0.04%
Covered Lines:	8137
Relevant Lines:	8619

---

💛 - Coveralls

[RastoHu]

Testing

@harminius, @MarcelGeo

• are the "old" order_params still valid? For instance
  /v2/workspaces/<ws_id>/projects?page=1&per_page=10&order_params=disk_usage desc and
  /v2/workspaces/<ws_id>/projects?page=1&per_page=10&order_params=size desc returns the same response. In first url is order_param disk_usage (old) and in 2nd is size.
• when invalid order param is passed error is thrown -> NOT FIXED:
  /v2/workspaces/17498/projects?page=1&per_page=10&order_params=somarina_jak_mraky asc returns valid response

[MarcelGeo]

Testing

@harminius, @MarcelGeo

* are the "old" order_params still valid? For instance
  /`v2/workspaces/<ws_id>/projects?page=1&per_page=10&order_params=disk_usage desc` and
  `/v2/workspaces/<ws_id>/projects?page=1&per_page=10&order_params=size desc` returns the same response. In first url is order_param **disk_usage** (old) and in 2nd is **size**.

* when invalid order param is passed error is thrown -> NOT FIXED:
  /`v2/workspaces/17498/projects?page=1&per_page=10&order_params=somarina_jak_mraky asc` returns valid response

1. we can have both versions
2. we are adding just logs but sorting is not working with somarina -> you just become some data.