Adding .noDeserialize to Row.slice / Row.nameSlice

We were heaving an issue where already decoded data was ran trough the deserializers again when doing a slice.

Setting the `noDeserialize` key on the schema when creating new `Row` objects mitigates this.
I've added a couple of testcases that should catch this in the future.