* Add Timings for third-party session handlers.
These often cause WorldGuard to get blamed by timings.
* Add config option to turn off extra timings.
* Move relocation to the right build file.
* Move config to a map for potential future expansion.
* Calculate timing immediately per-factory.
Instead of on each handler creation.
This functionally reverts e5b76a5, though individual classes can change
this behavior on an individual basis by overriding the method.
Also, make time-lock and weather-lock restore only initial values,
which should be more intuitive behavior when multiple regions overlap
with different flag values.