Reload conserver on service restart to bring up console on retry of failed deployment

We previously removed all references to the reload conserver handler because it is already executed by the conserver-server role when the conserver configuration file changes. However this introduced a bug where fixing and retrying a failed deployment (for example, one where a variable like epics_version was not defined in the first run) would cause the IOC to be deployed successfully, but not show up in console -u or show up as down.

This bug is caused by the fact that in the conserver role, the handler is only notified when the IOC list changes. However, we also need conserver to be reloaded in the case where the IOC list has not changed but the IOC unix socket has become available (like in the case of a retry).