refs #156

refs #129

refs #126

refs #154

Users weren’t able to create a time slot in the calendar if the slot
has already begun.

The logic now checks if the start time is later or equal to the start of
the slot of the current time (i.e. current time is 16:37:28, check is
performed against 16:30:00 for a 15 minute calendar slot size). This
prevents users from creating slots in the past but allows them to create
time slots within a slot that has already begun.

If the slot has already begun then the start time of the new time slot
is set to the next available 5 minute slot after the current time. This
means that if the current time is 16:37:28 and one creates a time slot
in the 16:30:00 - 16:45:00 slot window the start time of the new time
slot is set to 16:40:00.

fixes #167

fixes #151

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.

The useServerErrors function returns an object with optional keys. This
is fine sometimes but it would be nice to have individual variables
containing errors for each field and more importantly we need to display
errors than cannot be mapped to an individual form field.

Using a string key begs for conflicts.

API object attribute names are now:

1. camelCased (#164)
2. use Id / Ids suffix for object references (#172)

FEAT(gitlab-ci):Push from Feature Branch

See merge request !13

Image uploads might take a while and even though we can’t currently show
a progress bar for the upload (because fetch upload progress is still
not a thing) we can at least indicate that something is happening and
disable any interactive UI elements.

refs #144

isProcessing seems more general purpose as it’s not clear if the
provided function actually loads something.

As we wrap an async function we must await it. Otherwise finally is
called immediately.

Any environment that doesn’t have npm installed will immediately throw
an error because VERSION is set immediately.

closes #137