`GET` object optimization over the placement vectors

[carpawell]

this is an interesting topic at the intersection of different dimensions

let's try to base the behavior on writing and reading on the same basis. I expect both ops to iterate over same sequence of nodes (unless reading actually ends after the 1st success)

may be current implementation of SuccessAfter is not the most efficient one. If placement vector is

N1 [N2, N3]
N4 [N5]

then object is most likely on N4 than N2-3. Currently, we'll go over N1, N2, ...

in total, could we completely replace SuccessAfter with introduced WithCopiesNumber one for read ops? i guess so

Originally posted by @cthulhu-rider in https://github.com/nspcc-dev/neofs-node/pull/2607#discussion_r1343918367