starting TCP listener should be before DHCP4_STARTED
When kea starts with blq it logs:
2023-05-25 07:31:50.755 INFO [kea-dhcp4.dhcp4/4119.139754391320480] DHCP4_STARTED Kea DHCPv4 server version 2.3.8 started
2023-05-25 07:31:51.756 DEBUG [kea-dhcp4.tcp/4119.139754391320480] MT_TCP_LISTENER_MGR_STARTED MtTcpListenerMgr started with 8 threads, listening on 192.168.50.252:67, use TLS: false
Looks like Kea is starting TCP listener after it says it's started. And it should be before DHCP4_STARTED
message.
Background: in each forge test after Kea is started it is looking for DHCP4_STARTED Kea DHCPv4 server version 2.3.8 started
(or DHCP6_STARTED Kea DHCPv6 server version 2.3.8 started
message to continue with the test. When test start to send TCP messages at the beginning it fails with error connection refused. So kea is logging DHCP4_STARTED message before it's actually ready to work.