Misc

Small bugfixes, cleanups, test speed-ups, re-enabling compiler warnings, polishing.
The configuration being read will happen on every single policy update. I do agree that if the policy is not read, someone should know about it, but it can only happen in these cases:

* There is some error while loading it. This can be warned about separately, without the NOTIFY message in question.
* There is some error which means cf-serverd doesn't pick it up. This is a bug on our side, and bombarding the user with "Rereading policy file" in the hopes of finding the message to be absent at some point is not very considerate to the user.
* The policy has in fact, for some reason, not been updated on disk. This can be easily verified by other means, and again we are looking for the absence of a message.

In all of these cases, we are logging a lot of "success" messages in the hopes of finding the message absent later. IMHO not appropriate for default log level. If there really is a problem, the user can always switch to INFORM to debug the problem.