bug: discv5/discover.go messages flooding the docker DEBUG logs

[fbarbu15]

Describe the bug
In some cases the discv5/discover.go are flooding the logs with ~100 messages / sec and it's hard to follow anything.
This was fixed in the past but seems to have resurfaced: #881
I have 2 examples bellow, one where the issue reproduces and one where it does not.

Issue reproduces:

• node args:
  '--listen-address=0.0.0.0', '--rpc=true', '--rpc-admin=true', '--rest=true', '--rest-admin=true', '--websocket-support=true', '--log-level=DEBUG', '--rest-relay-cache-capacity=100', '--websocket-port=7970', '--rpc-port=7968', '--rest-port=7967', '--tcp-port=7969', '--discv5-udp-port=7971', '--rpc-address=0.0.0.0', '--rest-address=0.0.0.0', '--nat=extip:172.18.205.44', '--min-relay-peers-to-publish=1', '--legacy-filter=false', '--relay=true', '--discv5-discovery=true', '--peer-exchange=true', '--nodekey=30348dd51465150e04a5d9d932c72864c8967f806cce60b5d26afeca1e77eb68'

• log: node_with_fload.log

Issue doesn't reproduces:

• node args:
  '--listen-address=0.0.0.0', '--rpc=true', '--rpc-admin=true', '--rest=true', '--rest-admin=true', '--websocket-support=true', '--log-level=DEBUG', '--rest-relay-cache-capacity=100', '--websocket-port=35033', '--rpc-port=35031', '--rest-port=35030', '--tcp-port=35032', '--discv5-udp-port=35034', '--rpc-address=0.0.0.0', '--rest-address=0.0.0.0', '--nat=extip:172.18.11.6', '--min-relay-peers-to-publish=1', '--legacy-filter=false', '--relay=true', '--discv5-discovery=true', '--discv5-bootstrap-node=enr:-Ly4QLx0eOMbcRQ_K6bMnLPX9w9cHqJM6-nbGHxek5FYq_VvXo89njdHksTUyFamQQaqutmWsNiDbOfBOcqLRjlkmCSGAYv7MwHOgmlkgnY0gmlwhKwRAAKKbXVsdGlhZGRyc5gACgR_AAABBh8i3QMACgSsEQACBh8i3QOJc2VjcDI1NmsxoQM3Tqpf5eFn4Jztm4gB0Y0JVSJyxyZsW8QR-QU5DZb-PYN0Y3CCHyGDdWRwgh8jhXdha3UyAQ', '--peer-exchange=true'

• log: node_without_fload.log

go-waku version/commit hash

wakuorg/go-waku:latest

[fbarbu15]

Seems there's still one log that floods the docker logs:
node has no shards registered
node1_2023-12-13_14-26-09__2e5a7b17-7a3a-4811-b3a6-11406583d9a1__harbor.status.im_wakuorg_go-wakulatest.log