Bug description
When we use vshard on Tarantool 3, and one storage in unreachable, router starts spamming "Connection refused" messages with quite big rate (6 messages per second on my case) and will not stop until connection is established.

• OS: [e.g. Linux/MacOS/FreeBSD/OpenBSD]
• OS Version: [e.g. Debian 11, FreeBSD 11]
• Architecture: [amd64, arm]

Place tarantool --version output here.
tarantool version
Tarantool 3.2.0-0-g6df312b
Target: Darwin-arm64-Release
Build options: cmake . -DCMAKE_INSTALL_PREFIX=/opt/homebrew/Cellar/tarantool/3.2.0 -DENABLE_BACKTRACE=TRUE
Compiler: /usr/bin/clang /usr/bin/clang++
C_FLAGS: -fexceptions -funwind-tables -fasynchronous-unwind-tables -fno-common -Wformat -Wformat-security -Werror=format-security -fstack-protector-strong -fPIC -fmacro-prefix-map=/tmp/tarantool-20240827-9162-lgxxba/tarantool-3.2.0=. -std=c11 -Wall -Wextra -Wno-gnu-alignof-expression -Wno-cast-function-type -O3 -DNDEBUG
CXX_FLAGS: -fexceptions -funwind-tables -fasynchronous-unwind-tables -fno-common -Wformat -Wformat-security -Werror=format-security -fstack-protector-strong -fPIC -fmacro-prefix-map=/tmp/tarantool-20240827-9162-lgxxba/tarantool-3.2.0=. -std=c++11 -Wall -Wextra -Wno-invalid-offsetof -Wno-gnu-alignof-expression -Wno-cast-function-type -O3 -DNDEBUG

tt version
Tarantool CLI version 2.4.0, darwin/arm64. commit: 060408f

Steps to reproduce

1. tt init
2. tt create vshard_cluster --name spam_log_example
3. tt start
4. tail -f spam_log_example/var/log/router-001-a/tt.log (in other console)
5. wait until vshard bootrapped
6. tt stop spam_log_example:storage-001-a
7. see spam logs

2024-09-02 18:19:15.564 [65011] main/124/localhost:3301 (net.box)/box.net_box net_box.lua:309 W> localhost:3301: connect, called on fd 30, aka 127.0.0.1:58682: Connection refused
2024-09-02 18:19:15.564 [65011] main/117/localhost:3301 (net.box)/box.net_box net_box.lua:309 W> localhost:3301: connect, called on fd 26, aka 127.0.0.1:58683: Connection refused
2024-09-02 18:19:16.065 [65011] main/117/localhost:3301 (net.box)/box.net_box net_box.lua:309 W> localhost:3301: connect, called on fd 26, aka 127.0.0.1:58689: Connection refused
2024-09-02 18:19:16.065 [65011] main/139/localhost:3301 (net.box)/box.net_box net_box.lua:309 W> localhost:3301: connect, called on fd 30, aka 127.0.0.1:58690: Connection refused
2024-09-02 18:19:16.065 [65011] main/124/localhost:3301 (net.box)/box.net_box net_box.lua:309 W> localhost:3301: connect, called on fd 33, aka 127.0.0.1:58691: Connection refused
2024-09-02 18:19:16.568 [65011] main/117/localhost:3301 (net.box)/box.net_box net_box.lua:309 W> localhost:3301: connect, called on fd 26, aka 127.0.0.1:58696: Connection refused
2024-09-02 18:19:16.568 [65011] main/139/localhost:3301 (net.box)/box.net_box net_box.lua:309 W> localhost:3301: connect, called on fd 30, aka 127.0.0.1:58697: Connection refused
2024-09-02 18:19:16.568 [65011] main/124/localhost:3301 (net.box)/box.net_box net_box.lua:309 W> localhost:3301: connect, called on fd 26, aka 127.0.0.1:58698: Connection refused

Actual behavior

A lot of useless logs on high log level, higher than info.

Expected behavior
Less logs or may be these logs on lower level (verbose or debug).