Notification Debuggability

[mohityadav766]

Currently, we have difficulty tracking the state of a changeEvent in case of failure. We need the following information to be built so it RCA for failed message become easy.

• [x] Tracking the current state of publisher , the available event in the queue(change_event table) and the current offset run for the publisher.
• [x] Each publisher can have n destination and it is crucial to differentiate the event failed for which destination , we have consumer_dlq that can be utilized , but as of today that is working at the consumer level and not at the destination level.
• [x] Adding Test Message for all Slack, MsTeams , Email , to allow users to test working functionality while create the alerts.
• [x] Provide api for errored event , with the failureContext and also for which destination that particular event failed

[Siddhanttimeline]

Adding Test Message for all Slack, MsTeams , Email , to allow users to test working functionality while create the alerts.

Test Alert Destination PR Improvement iterations will follow.