Events Keep Publishing on Data Update/Delete Errors

[OguzErdi]

Description
When an exception occurs in the application, the event loop does not stop for both outbox events and missing events. Thus, if a single event encounters an error, other events continue to be published as expected.

However, when there is an issue with updating or deleting data, the same events get published continuously without stopping. To handle these types of errors, the Circuit Breaker pattern can be used to stop continuously publishing.

Expected Behavior
If an event fails due to an update/delete issue, the daemon should stop processing to prevent infinite retries.
The circuit breaker should properly detect and halt the affected daemon.

Steps to Reproduce
Trigger an event that encounters an update/delete failure.
Observe that the same event keeps getting published indefinitely.
Circuit breaker does not activate to stop the daemon.

Possible Solution
Ensure that the circuit breaker correctly detects persistent update/delete failures and stops the affected daemon.

[OguzErdi]

#18 the feature implemented, but there is a place for improvement. The daemons checks every RedeliveryDelayAfterError(250ms) to see if circuit breaker’s DurationSc(10mn) is up. We don't need that, should be fixed.