ZGW UX improvements: select document type

[sergei-maertens]

Closes #4606 (partially

TODO

• [x] Implement API endpoint to return available document types
• [x] Implement registration plugin runtime behaviour changes
• [x] Automatically select best version of document type

Changes

• [x] Allow selecting the document type in a dropdown after the case type is selected
• [x] Registration prefers the new config option if set, otherwise fall back to legacy behaviour

Checklist

Check off the items that are completed or not relevant.

• Impact on features

  • [x] Checked copying a form
  • [x] Checked import/export of a form
  • [x] Config checks in the configuration overview admin page
  • [x] Problem detection in the admin email digest is handled

• Release management

  • [x] I have labelled the PR as "needs-backport" accordingly

• I have updated the translations assets (you do NOT need to provide translations)

  • [x] Ran ./bin/makemessages_js.sh
  • [x] Ran ./bin/compilemessages_js.sh

• Commit hygiene

  • [x] Commit messages refer to the relevant Github issue
  • [x] Commit messages explain the "why" of change, not the how

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.61%. Comparing base (577b0df) to head (fe771da). Report is 19 commits behind head on master.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #4817 +/- ## ======================================= Coverage 96.60% 96.61% ======================================= Files 749 749 Lines 25563 25616 +53 Branches 3383 3394 +11 ======================================= + Hits 24696 24749 +53 Misses 604 604 Partials 263 263 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[robinmolen]

I was wondering, if you still wanted to change the catalogueUrl calculation/usage in the BasicOptionsFieldset.js (you said last week, in my PR of the ZGW products, that you wanted to try something different)

[sergei-maertens]

I was wondering, if you still wanted to change the catalogueUrl calculation/usage in the BasicOptionsFieldset.js (you said last week, in my PR of the ZGW products, that you wanted to try something different)

Yes, but I'll do that when I get to the medewerker roltype field, since that probably also requires it! So out of scope for this PR, in scope for the next one.