(vitineth/feature/workflow): adding ops planning workflow with additional upgrades

Across all elements this includes:

hub

Adds support for searching by state set
- This now allows you to specify an array of states and return events which contain at least one of those states. This is used to back the ops planning workflow to retrieve all events based on their states
Adding event reservation support
- This allows events to be submitted but not reserve the space. This is not rolled out fully into the system yet and needs some integration into the frontend and when the admin interface gets built there will be a default option. This will allow it to either act like the old system (anyone can book overlapping events) or like the new system (a booking request reserved the space)
Integrates an entire new AMQPlib based logging system
- This is presently integrated with greylog locally but could be linked into any system - there is no official solution here.
Adding request ID to logging
- This allows correlational tracking through all services

Adds ops planning workflow
- This will list all records that are in the review states or do not have the space reserved.
Adds new calendar to the frontend
- This new calendar models the google calendar layout including record stacking and seems to work pretty well. This will allow you to get a better overview. This needs some additional tweaks to integrate more fully
Makes frontend more modular for events and venues
- This allows displaying an already loaded element, not pulling it again from the API. This needs to be rolled out further to other view pages but is working well
Adds venue chips to the frontend
- Name describes them, a better way to view the venues on the event view pages and more
Removes user linking from comments
- User pages are not important and have been removed from the plans from the time being
Remedies tab pane sizing on frontend
- They now fill the page

Adding configuration to gateway
- Configuration is backed by mongodb in a new collection.
Adding review states with associated routes
- Review states are added into the configuration in the database and there is a general config object through which these values will be pulled. It only has get paths right now, these will be extended further when the admin interface is built
Adding basic request caching to speed up loading
- This is not an ideal solution but caching will be a bigger job so needs to be moved over to a new feature branch