Hot fix: Make sure the cache contains session details when using `event/query` API

Sometimes event/query requests fail with a 403 and sometime with 200. The problem does not occur in a local installation

Given icat+ is cloned 5 times in production, it can happen that the login step is done on one instance, and the event/query step on another. The event/query step needs to access session details in the cache. We need to make sure the cache gets populated with the session details associated to the incoming request before handling the event/query request.

This is done by adding the requiresSession middleware.