Consistently handle log topics and data ownership

[garyschulte]

Fix to consistently deinit/free log items and topics.

This enables a clean fix for ~700 zevm-stateless spec-test failures and ~300 skipped tests.

---

Note

Medium Risk
Touches memory ownership and lifecycle of EVM logs, including new heap copies of log data and broader cleanup paths on reverts/commits; mistakes here could cause leaks or use-after-free. Scope is localized to log emission and teardown but affects many execution paths.

Overview
Unifies EVM log ownership and cleanup. primitives.Log now owns heap-allocated data and topics (when non-empty) and provides Log.deinit() to free them.

LOG opcode emission (host_ops.zig) now heap-copies the log data slice (previously referenced interpreter memory) so logs remain valid after interpreter teardown, and all log cleanup sites (JournalInner.deinit, commitTx, discardTx, finalize, checkpointRevert, and ExecutionResult.deinit) are switched from manual topic frees to calling log.deinit() (also ensuring discarded logs on checkpoint revert are freed).

^{Written by Cursor Bugbot for commit 439e867. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.