[codex] fix OmniLogic compressed response boundaries

[djrobx]

What changed

Applies the protocol-level boundary fix in the integration compatibility layer:

• trim multi-part responses to the controller-provided MsgSize;
• do not strip trailing zero bytes before zlib decompression.

Why

The prior streaming fallback kept the integration working, but the source problem is the rstrip(b"\x00") heuristic. A valid zlib trailer can end with 0x00; removing it makes a complete response look truncated. The controller already declares the exact response length in its lead message.

The new code uses that length and keeps one-shot zlib decompression strict. It continues to accept protocol padding after a completed zlib stream and rejects truly incomplete compressed data.

Validation

• synthetic valid-zlib-trailer regression check
• Python compilation and Ruff lint/format checks
• live Tera controller refresh using the exact-boundary implementation (MsgSize=3937, reassembled payload 3937 bytes)

The separate upstream library fix is tracked in cryptk/python-omnilogic-local#153. This compatibility code can be removed once a released library contains that fix.