refs #146

refs #121

refs #155 #156

Submitting a note would sometimes fail but user’s were not informed that
something went wrong, because errors not mapped to any form fields were
not displayed.

closes #137

closes #141

This can be used in views to parse the error state from steering
responses.

closes #139

refs #89

closes #133

We’ve decided to move the show selector into the navbar because the
selected show is the primary state of the dashboard from which almost
all other state is derived.

Apart from that we now have support for filtering the list based on
active and inactive shows (and possible other criteria in the future) as
it was suggested in #122.

The playlist data is only available for the currently selected show. Any
playlists used in other shows will not be available and we should
gracefully handle that.

This is a quick fix to address #132. A more permanent and helpful
resolution is outlined in #135 and #136.

This is a stopgap measure until we’ve worked on #17 [1] and added a
management interface for simple models like funding categories and show
types.

refs #97

[1] #17

Up until now we had two different show selectors based on the number of
shows that were available. We now use the same show selector for any
number of shows.

Apart from that shows are now sorted
 1. based on their active state (descending, so inactive last) and
 2. their name (ascending, so A-Z)
in the show selector so it’s easier to find relevant shows.

Other changes:
* title handling has been moved into PageHeader component
* calendar management has been removed and is now handled
  locally in the EmissionManager component
* inactive shows are badged

refs #122

vue-full-calendar is not the official Vue package of fullcalendar, is
only compatible with Vue 2.x, uses the outdated fullcalendar v3 library
and contains a bunch of huge dependencies like jQuery and moment.

The changes in this commit migrate the dashboard to fullcalendar v5 and
the official vue component. Apart from that there have been a few
refactors and fixes. These are:

* remove irrelevant stub event callbacks
* make view updates reactive instead of imperative
  (see removal of renderView method and introduction of renderWatcher)
* rename methods to better reflect their purpose
    resolve → enterConflictMode
    resolveEvent → resolveConflict
* emit events in modals instead of call to methods on this.$parent
* let → const where applicable to prevent accidental reassignments
* switch to for-of loops (from for-in) for better readability
* fix some typos

One other major change is that timeslot and collision data is no longer
mixed with event data for fullcalendar and is assigned to the
extendedProps property instead. As mentioned in fullcalendars
documentation on event parsing [1], any data that fullcalendar does not
handle on its own is moved into the extendedProps object with the
explicit recommendation to put them there right from the start. We
follow that recommendation.

closes #94

[1] https://fullcalendar.io/docs/event-parsing

The steering API returns HTTP 400 errors for general payload and 409
errors for scheduling conflicts that we didn’t handle yet.

fixes #93

The steering API has some deprecated attribute names that we should no
longer use. These are:

  dstart → first_date
  until → last_date
  tstart → start_time
  tend → end_time
  byweekday → by_weekday

These changes in naming have also been applied to variable names,
attribute names and translatations in the dashboard code in order to
avoid confusion.