Record Kea configuration hash and detect no config change

Stork is periodically pulling configurations from Kea. To prevent repeating CPU intensive examination of the received config we should first compare the hashes of the existing and new config. That way we can easily detect whether the configuration remains the same and skip the update altogether. When the config change has been detected, we can also emit an event.

This will to some degree address #353 (closed).