Support SELECT ALL semantics for selectors

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

I'd like to filter out all nodes with some filter and then use all of them in a selector. Looks like there is no way to do that now, I have to specify some count.

This is especially annoying in cases like some on-prem/cloud policy where I'd like to store a copy locally and a copy in a more cloudy environment. I may have a storage node locally, so I'd create a container with SELECT 1 and REP 1. Then I will add a machine to my local environment, but it won't be used for this container.

Describe the solution you'd like

It seems like this behavior could be achieved without neofs-api changes, just by some special treatment of SELECT 0 (which doesn't make sense otherwise anyway).

Maybe there are other options, let's talk about them here, if SELECT 0 is OK then I'll create an issue in neofs-sdk-go to have SELECT ALL as another way of writing SELECT 0.

Start by reviewing the selector semantics in neofs-api and the referenced neofs-sdk-go handling of SELECT 0. Compare the proposed SELECT 0 behavior with the desired SELECT ALL semantics and determine which API or SDK definitions would need agreement. Done means the representation and compatibility behavior are clearly specified.