Time-based caching of overflows UUIDs of advertisement data

[Supereg]

Problem

Currently, we only consider the advertised service UUIDs in the main advertisement packet and do not consider the service UUIDs as part of the overflow area which is send in some intervals.
#41 already updated to also consider the overflowServiceUUIDs of the current AdvertisementData instance. However, the overflow area might not always be sent and therefore the overflowServiceUUIDs might be periodically overwritten by new advertisements.

Solution

We need to retain the overflowServiceUUIDs of previous advertisements. However, we also need to release them after a certain amount of time as otherwise we wouldn't detect a peripheral that stopped advertising a service that was previously part of the overflow area.

Additional context

It might make sene to research more in-depth, how the overflow area exactly works and in which intervals it is sent to decide what a good maximum timeout is.

Code of Conduct

• I agree to follow this project's Code of Conduct and Contributing Guidelines