TBinaryProtocol returns error size when zerocopy is on and the impl doesn't use LinkedBytes

Currently only LinkedBytes supports zerocopy, but the length calculation can't be specialized for LinkedBytes.

This relies on https://github.com/rust-lang/rust/issues/31844, when this is stabilized, we can fix the problem.

No file, test, or entry point is named. Trace TBinaryProtocol's length calculation and the LinkedBytes zerocopy path, then review Rust issue 31844 because the proposed fix depends on that stabilization. Done means the error size is correct when zerocopy is enabled even when the implementation does not use LinkedBytes.

Written by the indexing model from the issue text.