Retry strategey for NotificationService#sendNotifications
At the moment, no retry strategy for failed Notifications is implemented. Given the following scenario, host is not vailable any longer, e.g.
2024-01-16 22:39:13,449 WARN [org.ope.neo.ser.NotificationService] (executor-thread-405) Unable to send notification [https://localhost:8080/logistics-objects/_data-holder/notifications/55d16a32-17b3-4d90-96cf-bd75d86ce0a2] to [https://1r.example.com/]
it could be helpful to have a setting like
send-notificiations.max_retries=3
to configure the maximum attempts to send a particular Notification to a subscriber.