Paraply should wait for events to propagate into db before redirecting users

[snorremd]

Right now there is a race condiction where a user will be redirected to the home page (event list) after submitting an event before that event is properly inserted into the db. The cause might be that an async function is ignored and the response written before the setEvent finishes.

It might possible also be caused by ElasticSearch not updating the cache of the event index before the new getEvents query is submitted when the user is redirected.

Will have to look into this.