GHSA-xhj4-g6w8-2xjw: go-zserio has Unbounded Memory Allocation for All Platforms

Severity: Critical

CVSS Score: 9.8

### Impact When deserializing arrays, strings or bytes (blob) types zserio first reads the size of the variable, and then allocates sufficient memory to load data. Since the size is always trusted this can be abused by creating a data file with a large size value, causing the zserio runtime to allocate large amounts of memory. ### Patches Please apply [this commit](https://github.com/woven-by-toyota/go-zserio/commit/39ef1decde7e9766207794d396018776b33c6e45). ### Workarounds - Do not accept zserio data from non-trusted sources. - Use secure transportation protocols (like TLS).