network: disable_recv before telling actor to close connection

As of d62ad96, when the connection can't receive more data from the
client, it tells the actor to stop the connection and calls
disable_recv(). The actor operates in it's own thread and when it stops
the connection, disable_recv is being called again from a different
thread. Since the actor is told to stop the connection before
disable_recv is called, the two calls to disable_recv may happen
simultaneously.

This causes a race condition issue where both threads can reach past the
check that recv_id is not None before either of them set it to None. If
one of them set it to None before the other one tries to use it, an
error is raised.

This commit calls disable_recv before telling the actor to stop the
connection. Since disable_recv is a blocking call, this ensures that
recv_id is being set to None before the actor thread begins to stop the
connection.

Fixes #781
tests: Test call order in test_recv_callback_gets_no_data
main: Log uncaught exceptions

(cherry picked from commit 027b7a53fe9212853062da352c464c4277ade510)
Merge pull request #827 from trygveaa/fix/network-thread-issue

network: disable_recv before telling actor to close connection
backends: Update browse() signature and docs to match core implementation

Fixes #833
local: Add ROOT_DIRECTORY_URI constant

Related to #833
Merge branch 'release/v0.19.x' into develop
local: Move constant to Library class

Related to #833
Merge branch 'release/v0.19.x' into develop
http: Guard against double close of WebSocket
Merge branch 'release/v0.19.x' into develop