Add WS route to get the running actions

[johhnry]

If the Socket server is disconnected while actions are running, it loses them when reconnecting and so the front-end.

Between the UI and SSS we have: /ui/getRunningActions which returns a dictionary of actions:

getRunningActions: WithCallback<
  ServerResponseWithData<{ [uuid: string]: Action }>
>;

then when the UI starts up, it sends that query to get the current running actions. In this case the either silex_client should send the actions to the SSS when reconnecting (we can use the reconnection event) or the other way around?