109 filter sort

[Ryaken-Nakamoto]

ℹ️ Issue

Closes #109

📝 Description

Did a bit of bug bashing to run the backend. Not sure if it was running on your end, but after pulling from main I made the following changes:

1. Added Relation<> to prevent circular dependencies
2. Changed migrations to *.js from *.ts to enable node to target compiled output
3. added missing dependencies to various .module files

There was also a preexisting linting error for importing to the backend from the frontend. I disabled it for now with a // eslint* comment, unsure how you want to handle this.

EDIT AFTER PR REVIEW: Updated from 7 endpoints to 1 centralized endpoint to sort and filter. /filter-sort. Tested w/ no filters passed in, almost all of them passed in, and some in isolation. Also tested a case where an empty list was returned. Great callout from @GauriRajesh733 to change to this approach. Made all fields optional, thought it would have good ease of use for consumers of the service. Undefined/[] cases are handled in the service method.

P.S. if you have trouble running the tests I had to regenerate my lock file, didn't commit it but if that is an issue on your end that is probably the solution.

[GauriRajesh733]

looks really good!! im just thinking if we should have one route for filtering and sorting that takes in all criteria at once so that we don't need separate methods for each (something like AnthologyFilterDto and AnthologySortDto). i know initially in the ticket description these methods were separated so lmk if you have any questions or you think the current approach is more appropriate!