Fix TableLookup

[leekeiabstraction]

Purpose

Linked issue: close #185

Fix issue with TableLookup parsing being off by 2 columns

Brief change log

Fix TableLookup so that SchemaId field bytes are not passed to CompactedRow::from_bytes(), these fields can be skipped as current rust client implementation does not check schema and already passes row_type

Tests

Verified using example_kv_table.rs. Integration test to follow

=== Upserting ===
Upserted: GenericRow { values: [Int32(1), String("Verso"), Int64(32)] }
Upserted: GenericRow { values: [Int32(2), String("Noco"), Int64(25)] }
Upserted: GenericRow { values: [Int32(3), String("Esquie"), Int64(35)] }

=== Looking up ===
Found id=1: name=Verso, age=32
Found id=2: name=Noco, age=25
Found id=3: name=Esquie, age=35

=== Updating ===
Updated: GenericRow { values: [Int32(1), String("Verso"), Int64(33)] }
Verified update: name=Verso, age=33

=== Deleting ===
Deleted: GenericRow { values: [Int32(2), String(""), Int64(0)] }
Verified deletion

[leekeiabstraction]

@luoyuxia @AndreaBozzo Appreciate if you can review here

[AndreaBozzo]

LGMT, comment is more of a personal question

[AndreaBozzo]

more of a brainstorming for later, on paper can still panic if the response is smaller than 2 bytes right?

[leekeiabstraction]

Good question. That is right, however that would be an unexpected case. I would expect that schema id field and header to be there, having said that, making this more defensive by returning Error would be a good improvement to make

[luoyuxia]

+1