browse/utils: Properly fix the issue with file-magic

Finally manage to remove the ugly hack I introduced in a2759fec. Turns out
that calls to file-magic API are not thread-safe so they must be protected
with a threading.Lock instance.