Offboard from ObjectOutputStream to custom writer or use reset

Object output stream comes with an overhead of object cache which doesn’t make much sense for AOF as each command is independent. This leads to memory leaks and also slows down reads and writes.
Since we are already writing byte stream we don’t need specific serialisation capabilities.

No files, tests, or entry points are named. Start by locating the AOF code that uses ObjectOutputStream and inspect how commands are written and read. Done should remove unnecessary object-stream caching, or apply reset safely, while preserving independent command handling and improving the stated memory and I/O behavior.

Written by the indexing model from the issue text.