feat: filter and sort backend

[Xtrah]

Closes #56

Summary of changes

Filter applications based on queries

• GET /applications?name=[query]
• GET /applications?status=[status] status: all possible statuses (is also validated) e.g. Pending
• GET /applications?sort=[sort_attribute] sort_attribute: name_asc, name_desc, date_asc, date_desc
• GET /applications?committee=[committeeID] can be repeated e.g. (committee=3&committee=10)

This also includes validation of queries,:

• Name only accepts strings
• Status only accepts strings within the StatusTypes-enum
• Sort only accetpts strings within the SortType-enum
• Committee only accepts integers

[LiviaValenti]

I can't seem to find the possibility to assign you as reviewer @Xtrah as you created this PR. So this tag represents a request for review 🤺

[SanderArntzen]

I can't get this solution to work. The name-filter partially work, committee-filter don't work, status-filter partially work, and sort dosn't work. I tested through Postman. When I say don't work/partially work, I mean that it either returns all applications, or some applications, but not the right ones, or no applications at all, even though it should return at least one

[LiviaValenti]

Outdated:

Current: ⚠️ committee and not committees as a query param

Previous: ⚠️ committees and not committee as a query param

I changed that without updating the PR description. @SanderArntzen can you test again after the page-default fix and present concrete test-cases :0 ?

Here is an example-query that should work as expected if you have any applications sent from people with name that contains 'Liv' that is to a committee with id 5: http://localhost:8082/applications?name=Liv&committees=5&order=date_desc

[SanderArntzen]

Nice jobs! Works as expected

[Xtrah]

Amazeballs 🤩