mod_firewall: Initialize compiled chunk just once for all handlers This should fix a case where some stateful dependencies (such as throttles) produce separate instances for every call to new_handler(), leading to surprising behaviour (e.g. rules executed via JUMP CHAIN vs ::deliver would have separate rate limits). This also adds better error handling in case the compiled code fails to run for some reason.

---
summary: Storage benchmark tool
...

To benchmark `mod_storage_internal`:

    prosodyctl mod_benchmark_storage internal

Does a number (aprox. 10000) of reads and writes and to the selected
storage driver and tells you how long it took.