Status code may lead to client cache invalidation

[carpawell]

Is your feature request related to a problem? Please describe.

Saw in logs:

2024-03-01T17:28:48.160Z	info	cache/multi.go:212	invalidated cached clients to the node caused by the error	{"address group": ["/dns4/s03.neofs.devenv/tcp/8080"], "error": "/dns4/s03.neofs.devenv/tcp/8080 node client: status: code = 2052 message = object already removed"}

Describe the solution you'd like

Do not drop connections because of status errors. Status response means that node responds.

Describe alternatives you've considered

Do not have any.

[carpawell]

Also

2024-03-01T17:35:54.417Z	info	cache/multi.go:212	invalidated cached clients to the node caused by the error	{"address group": ["/dns4/s04.neofs.devenv/tcp/8082/tls", "/dns4/s04.neofs.devenv/tcp/8080"], "error": "/dns4/s04.neofs.devenv/tcp/8080 node client: status: code = 1024 message = node outside the container"}