Starting the timesvc by default negatively impacted test-results of advapi32:ServiceNetwork, iphlpapi:GetExtendedUdpTable, iphlpapi:GetOwnerModuleFromUdpEntry

I noticed that by chance when I applied the following workaround:
0.4.14-release-105-g3066a9a (2024-04-07)
When the timesvc is not started, we do run more tests and we can succeed more of them also. The workaround affects the following components positively:
advapi32:ServiceNetwork
iphlpapi:GetExtendedUdpTable
iphlpapi:GetOwnerModuleFromUdpEntry
see the results:

0.4.14-release-104-g5f5ed42 vs. 0.4.14-release-105-g3066a9a :
KVM https://reactos.org/testman/compare.php?ids=94327,94534
VBox https://reactos.org/testman/compare.php?ids=94325,94533
This means my workaround does improve the older releases test-results (unexpectedly).

In return we can deduce that those tests broke by
0.4.13-dev-618-ge4898e6
from their former good state, to the still suboptimal state that we can see in todays master head 0.4.15-dev-7871-g5eea72f:
VBox https://reactos.org/testman/compare.php?ids=94526
KVM https://reactos.org/testman/compare.php?ids=94527