This way one can just run `npm run test` instead of using the make
target.

We now use the more flexible ErrorDetailArray data structure from
@rokoli/bnb which makes it harder to accidentally ignore or miss errors.

refs #257 #258

refs #116

refs #186

refs #242

Up until now the dashboard used a hardcoded list of rrules that matched
a long-gone fixture set of rrules in steering. Additionally, rrules were
translated in the dashboard using the the ID of the rrules in steering.
This means that any change to the fixture set, removing an rrule or not
importing the fixture set at all would mix up the translations and
therefore the actual schedules that people would create.

A few months ago the rrules were reworked and an API endpoint was
introduced that exposes the rrules defined in steering. No appropriate
change was made in the dashboard and so the rrule definitions got
out-of-sync.

This change implements a rrule store that fetches data from the API.
Additionally we’ve also implemented a custom rrule to natural language
mechanism [1]. This is because the scope of the rulesets we use in the
AURA radio context is well-known and not to complex and because rrule.js
built-in `toText` function, which might have been an option, is limited:

* bysetpos seems to be entirely unsupported
* internationalization will produce gramatically questionable
  output for languages like German, because the translation
  interface is somewhat lacking.

[1] #226 (comment 13669)

Modals will not show with Vue 3.4.
This is a bummer :(.

refs #140

refs #127

This component implements the logic for the standard
django-rest-framework (DRF) order parameter.

DRF uses plan field names for ascending and a "-" prefix for descending
order.

Example:
	if you’d want to sort by id you’d write:
		?order=id
	if you’d want to sort by id in reverse order you’d write:
		?order=-id

The OrderFilter supports arbitrary order fields, allows you to set the
sort direction (ascending, descending – configurable per order field)
and supports re-ordering of order fields so that that hierarchical
orders can be set.

This should make it easier to find icons, as they can now be included
directly as component:

<icon-... />

Icons can be found on: icon-sets.iconify.design

Example:
Icon at https://icon-sets.iconify.design/ph/trash/ can be used with the
following component:

<icon-ph-trash />

refs #89