Deserialization must fail if bytes remain after the last entry

[SavicStefan]

Require compact tuple sketch deserialization to consume the entire input buffer.

Adds a test for deserializing a wider summary as a narrower summary.

[proost]

Technically, you are right. But it can change implicit contract in the API.

[SavicStefan]

Technically, you are right. But it can change implicit contract in the API.

but like serialized format does not identify the summary type, so this is needed to detect that mismatch, wdyt?

[proost]

@SavicStefan
Now I understand your intention. you're right that the mismatch is undetectable from the format alone. But that's structural, not a gap to patch. See this.
It can't distinguish a wrong summary type from a larger buffer or a SerDe that over-report.

And also some users will be relying on it, This change would break them.

[leerho]

I agree with @proost on this. We can't assume that a given MemorySegment is dedicated to a sketch / Summary and nothing else. It is really up to the sketch and the user's code to figure out how many bytes to read. This is true of all our sketches that leverage MemorySegments.