[network] Possible performance improvement for performArpPing

[lsiepel]

Another issue with the current iOS wake up implementation is that it is part of performArpPing which is executed for every network interface. So it is executed many times if you don't restrict the number of network interfaces (#16145).

Originally posted by @wborn in #9575 (comment)

[wborn]

If iOS wake up is configured it could be put into its own CompletableFuture and after it completes the arping commands could be exectued, e.g. using thenRunAsync

[lsiepel]

Was briefly looking into this. I doubt there will be any benefit.

The wakeUpIOS is strictly tied to the performArpPing, e.g. it is a pre-requisite for the following nativeArpPing.

As this check is conditionally if (iosDevice) and the interfaces can be restricted. I have a hard time to see where there are optimisations left. wdyt?

[wborn]

IIRC it would optimize network traffic when using the default configuration and having lots of (Docker) interfaces.