Sometimes we want to query the API for certain objects. We can now do
that by passing a URLSearchParams object to list operations.

All requestInit arguments could have been undefined already, because we
declared it as an optional argument, but sometimes it’s nice to
explicitly skip the argument with `undefined` which is now possible as
well.

Sometimes we don’t have a static list of choices but an async source for
them (like an API endpoint). This is now supported out of the box
through the searchProvider prop.

refs #185

refs #185

Bootstrap only displays form group errors if the .invalid-feedback
element is preceded by a .is-invalid element. That is an uncessary
restriction and we can simply enforce the errors to be displayed if it
is rendered.

refs #181

Pinia store destructuring doesn’t work on the plain store object. One
has to use storeToRefs or keep the original store object.

see: https://pinia.vuejs.org/core-concepts/

internal note and show owners are both admin-controlled.

refs #146

refs #146

This way we can use the existing server error handling infrastructure
from the newer fetch-based API implementations.

Django rest framework would sometimes return objects like this

  { "email": ["Gib eine gültige E-Mail Adresse an."] }

which we didn’t properly handle.

refs #146