`ObjectRangeInit` does not return an error on an incorrect token verb

[tatiana-nspcc]

Current Behavior

ObjectRangeInit returns no error and an empty ObjectRangeReader when an incorrect token verb is used.

Expected Behavior

It should return a clear and understandable error.

Steps to Reproduce

I used a valid PrmObjectRange with VerbObjectGet instead of VerbObjectRange.

[roman-khimov]

Doesn't seem to be an SDK issue. Rather it's a node fallback, right, @carpawell, @cthulhu-rider? The question is if it's a feature or a bug. Refs or duplicates nspcc-dev/neofs-node#3547.

[cthulhu-rider]

most likely. But having

an empty ObjectRangeReader

this can be considered legit for empty object only. Is this the case @tatiana-nspcc?

[tatiana-nspcc]

No, the object wasn’t empty, I verified this using ObjectGetInit, which returns the full object. It was 1000 randomly generated bytes.