Remove byte dumps from accepted chat packets

Follow up the chat crash investigation by removing routine inbound/outbound chat packet byte dumps, including direct MsgTell serializer/deserializer console output. Preserve unknown/rejected packet diagnostics and packet dispatch/wire behavior. Do not expand into chat-content logging policy or framing changes. Acceptance: known accepted chat packets do not log payload bytes; unknown packet diagnostics remain; ChatEngine build and focused source inspection pass. Per user feedback, do not retain a dedicated logging test harness for this small removal. Implemented in the existing chat disconnect worktree/branch; follow-up committed as 8013c5e76 and pushed to pull request #2945: https://git.project-rk.com/prk/engines/pulls/2945. Removed inbound routine hex output, outbound Trace hex output, and MsgTell serializer/deserializer console dumps. Packet-type metadata remains at Trace. Unknown-handler dumps remain; failed known chat handlers now dump in the exception path rather than for every packet. Validation: ChatEngine build passed with 0 warnings/errors; git diff --check passed; source inspection confirmed remaining byte dumps are error-path-only. Dedicated test harness was removed following user feedback. Textual tell-content console logs are unchanged (outside byte-dump scope).