Catch zmq socket_t::bind() failures on startup
Without this zmq socket_t::bind() failure is printed on stdout (and
difficult to track when started in background and with initscript)
Merge branch 'release_0.98.3' into release
Merge branch 'release_0.99.0' into release
Merge remote-tracking branch 'remotes/upstream/dev' into kraken_startup_exception
Add stay_in unittests.

Test in routing_api_test fails when it shouldn't... (?)
Test counter-clockwise vj-extension
Fix unit_test (no nex/prev vj without finish)
raptor_path don't add wait between two interling sections
Add more stay_in raptor_api unittests
Subtract amount of transfers at reconstruction vj_extension
Require VJ extensions to be direct
Add connections between teleport
Fix mistake
Fix very probably typo
Assert on reversal errors

If there are no solutions found at this point, a bug is present causing unsymetric searches in clockwise vs counterclockwise. If no paths exists, this assert will never be reached anyway after the invalid_idx check

--Do not merge as such a bug is present --
Add comment on reversal assert
Merge remote-tracking branch 'remotes/upstream/dev' into kraken_startup_exception
Take advices: only catch bind() calls and return 1
Add linenoise submodule
Raptor: refactorize single run