Harden KV protocol decoding to check for sane header values

Things to check for:

• Is the header consistent with the protocol. e.g.: a value that's huge but an extras that doesn't include flags
• Is the value beyond some level that makes no sense, say >256MB, is a clear issue. This may need to be tuneable
• datatype field
• get response that has a CAS of 0