systemd is not notified when chroot is in place

When unbound is ran as a systemd service and is also configured to chroot it may be the case that unbound cannot communicate to systemd through the `NOTIFY_SOCKET` that probably lives outside the chroot.
This leads to systemd thinking the unbound service is unresponsive.

Try to check if that is the case and warn the user.