libwurfl is thread safe

so we don't need a lock before accessing it , we just need to be careful
swapping the wurfl handler when reloading the database because of a SIGHUP
and this can be easily achieved using the atomic builtins (add_and_fetch/cmp_and_swap)
allow to still run in single-thread mode (if desired)