client: Detect invalid response message format

[cthulhu-rider]

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

currently, when Client receives protobuf message incompatible with the response structure, it returns invalid response signature. This happens because in this case proto decoder:

• returns no error;
• leaves decoded response untouched (empty)
• sets unknown fields in the decoded response

Describe the solution you'd like

when Client receives response message having known fields with broken format (e.g. wrong type), return clear error on this

note: some fields can be just unsupported (old client, new server). I did not check is it easy to distinguish broken fields from unsupported ones or not, so be careful: unsupported fields must not be denied in general for forward compatibility

Describe alternatives you've considered

do nothing. Technically, there is definitely no valid response signature. But nobody will know what the actual problem is

Additional context

Client testing. Following snippet can also be useful:

func TestInvalidResponseFormat(t *testing.T) {
	m := timestamppb.Now()
	b, err := proto.Marshal(m)
	require.NoError(t, err)
	var resp protoobject.HeadResponse_Body
	require.Error(t, proto.Unmarshal(b, &resp), resp)
}

=== RUN   TestInvalidResponseFormat
        	Error:      	An error is expected but got nil.
        	Test:       	TestInvalidResponseFormat
        	Messages:   	{state:{NoUnkeyedLiterals:{} DoNotCompare:[] DoNotCopy:[] atomicMessageInfo:0xc0002222a0} sizeCache:0 unknownFields:[8 185 193 225 186 6 16 142 250 191 211 1] Head:<nil>}