[#1653] morph: Handle chain notifications via pool

Handling notification in a synchronous manner may lead to a blocking state
if a handler uses neo-go client.

Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>

pkg/morph/event/listener.go

@@ -250,7 +250,12 @@ loop:
 				continue loop
 			}
 
+			if err = l.pool.Submit(func() {
 				l.parseAndHandleNotification(notifyEvent)
+			}); err != nil {
+				l.log.Warn("listener worker pool drained",
+					zap.Int("capacity", l.pool.Cap()))
+			}
 		case notaryEvent, ok := <-notaryChan:
 			if !ok {
 				l.log.Warn("stop event listener by notary channel")