ARCO-183: implement quarantine for problematic callback receivers

[arkadiuszos4chain]

Description of Changes

This update introduces a quarantine mechanism for receivers that fail to handle callbacks, helping to prevent repeated failed sends.

Changes:

• if a callback fails to send, the receiver is placed in quarantine
• during the quarantine period, all incoming callbacks for that receiver are persisted to storage
• the system periodically checks the stored callbacks and attempts to resend them once the quarantine period ends
• a cleanup process periodically prunes the store, removing outdated and unsent callbacks

Testing Procedure

• I have added new unit tests
• All tests pass locally
• I have tested manually in my local environment

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have updated CHANGELOG.md with my changes

[boecklim]

I think correct english would be quarantined_until, but not sure.
Thinking of naming I think the callback itself is not quarantined, but rather the URL.

What would you think of postponed_until?
IMO that would be a bit more expressive name of the field

[arkadiuszos4chain]

Agree, it's a better name.
Changed

[sonarqubecloud]

Quality Gate failed

Failed conditions
70.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud