[Bug] Node discovery / connect_peers_task_handler does not stop attempting already established connection

[felixbrucker]

What happened?

It seems like the node discovery and/or the connect_peers_task_handler does not stop attempting to connect to an already established connection.
I have my nodes added using the new full_node_peers config option, but get a lot of log spam from the start_client() method attempting to connect to it seemingly indefinitely, despite that connection already existing

Version

2.2.0

What platform are you using?

Linux

What ui mode are you using?

CLI

Relevant log output

2024-02-29T10:27:37.922 full_node full_node_server        : WARNING  cannot connect to 185.205.246.74, duplicate/self connection
2024-02-29T10:27:40.927 full_node full_node_server        : WARNING  cannot connect to 185.205.246.74, duplicate/self connection
2024-02-29T10:27:43.930 full_node full_node_server        : WARNING  cannot connect to 185.205.246.74, duplicate/self connection
2024-02-29T10:27:46.937 full_node full_node_server        : WARNING  cannot connect to 185.205.246.74, duplicate/self connection

[wjblanke]

OK we will look into this. It shouldn't cause much issue besides the log spam and minor load on the peer for the connection.