Expanded XCM Notification Event Types

[mfornos]

Broaden the scope of notification event types. Currently, the server notifies on success/failure executions on the destination chain. We intend to configure expanded notifications, including notifications on SEND events in the origin chain (success/fail/finalized), on HOP events in intermediate chains (e.g., message relayed on the relay chain in HRMP). Additionally, notifications on destination chains will cover events such as asset traps and non-received notifications (no message received within a configured time frame).

• [x] #19
• [x] #20
• [x] #21
• [x] #22
• [x] #23
• [x] #24
• [x] #28
• [x] #45

[mfornos]

To correlate HRMP messages, we should rely on the message id (i.e. setTopicId) which is not currently available.