Delivering acyclic requests into GenAP: Retry-mechanism should probably not just "give up and discard the packet" after a few failed attempts

Currently we implement a retry-mechanism for the data-avail hook into GenAP ("the GCI application") in case it can (temporarily) not handle our request. We retry with a certain hardcoded timeout period a (hardcoded) number of times until we give up and just drop the request, log an error into the logbook and call the error callback of GenAP ("the GCI application")

After internal discussion, "giving up" on an acyclic request is probably not an feasible option for us. It is ok to detect that situation and treat it as a (recoverable) error, but we should not give up retrying and probably also not escalate over the error callback (check back with the GCI documentation regarding the error callback).