XDCR - resolverSvc error handling

Currently, resolverSvc starts and initializes evaluator. There can be possibilities that the evaluator has problems and exits. XDCR currently prints an error message into the log, and that's it. This is fine for CC since CCR is POC. But for actual CCR release, it may be problematic since custom conflict will just silently fail and channels may be backed up and blocked.

XDCR needs to handle the resolverSvc starting error gracefully.