Concurrent orders - some edge cases doesn't work correctly

[eMeF1]

There are still some edge cases when it doesn't work. Specifically the sensor.[device]_delivery_time inherit the value from the announcement which may not always relate to the soonest order.

Furthermore when the announcement is cleared out on the endpoint, the sensor.[device]_delivery_time maintain the last value as long as binary_sensor.[device]_next_order_made is true since this is a logic to prevent that value to be cleared short before the delivery.

We could check if the announcement relates to the soonest order and if not we can fetch the data from the same source as sensor.[device]_delivery_slot_end which works OK.

Originally posted by @eMeF1 in #53 (comment)

[eMeF1]

Also right before delivery the announcement for the current delivery is replaced by the announcement for the next delivery which updates the sensor.[device]_delivery_time with the next delivery data while the first delivery is still in progress.