[#357] Refactor endpoints with search

[SilviaAmAm]

Fixes #357

The fix was a bit more invasive than expected.

I created a new search endpoint for the:

• Zaken endpoint
• Local zaaktypen choices endpoint

These endpoints do the same as the GET, but with a POST. The filter params then are passed into the request body instead of query params in the URL.

Since the Zaken list endpoint supports ordering and pagination, I had to support
passing these query params also through the request body.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 98.52941% with 1 line in your changes missing coverage. Please review.

Project coverage is 90.32%. Comparing base (9c9bfb4) to head (ec4d6bd).

Files with missing lines	Patch %	Lines
backend/src/openarchiefbeheer/utils/paginators.py	88.88%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #687      +/-   ##
==========================================
+ Coverage   90.26%   90.32%   +0.05%     
==========================================
  Files         211      211              
  Lines        6248     6286      +38     
  Branches      675      675              
==========================================
+ Hits         5640     5678      +38     
  Misses        608      608              

Flag	Coverage Δ
backend	91.07% <98.18%> (+0.05%)	⬆️
jest	32.71% <15.38%> (-0.03%)	⬇️
storybook	86.23% <100.00%> (+0.40%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[svenvandescheur]

Do we know where the issue originates from, and can't we fix it with a setting? This fix feels a little bit intrusive to me and introduces inconsistency. I guess that's ok if its really needed but I'd like to see if we can find a simpeler solution.

[SilviaAmAm]

Do we know where the issue originates from, and can't we fix it with a setting? This fix feels a little bit intrusive to me and introduces inconsistency. I guess that's ok if its really needed but I'd like to see if we can find a simpeler solution.

This was the problem that the different browsers were giving different errors. I don't think we can fix this problem with a setting, if the frontend makes a request with a humongous URL, things might break before it gets to the backend. This SO answer is quite informative: https://stackoverflow.com/a/417184/7146757

[svenvandescheur]

Is this still used or can we safely remove it?