object/searchv2: Keep full error message in the status response

Previously, `SearchV2` RPC server responded with the deepest Go error
message in the status message. To achieve this, the server made `errors
.Unwrap` to the lowest level. This approach was reused from other API
calls, so it brought up the same shortcomings to new search.

For example, CLI user could face following error:
```
rpc error: status: code = 1024 message = illegal base64 data at input byte 4
```
and only imagine which part of the request processing is an invalid
Base64.

This cancels error unwrapping for `SearchV2`, making it to respond with:
```
rpc error: status: code = 1024 message = invalid cursor: decode cursor from Base64: illegal base64 data at input byte 0
```
instead.

Note that previously existed RPCs are untouched to avoid system
destabilization. They will be considered separately.

Refs #2744. Refs #3058.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>

pkg/services/object/server.go

@@ -1883,7 +1883,7 @@ func (s *server) signSearchResponse(resp *protoobject.SearchV2Response) *protoob
 
 func (s *server) makeStatusSearchResponse(err error) *protoobject.SearchV2Response {
 	return s.signSearchResponse(&protoobject.SearchV2Response{
-		MetaHeader: s.makeResponseMetaHeader(util.ToStatus(err)),
+		MetaHeader: s.makeResponseMetaHeader(apistatus.FromError(err)),
 	})
 }