Reduce allocations required to enter a hook

When a method is called, an "event template" is cloned and passed into the hook to be mutated. The template serves as cache for all the static properties (src path, defined class, method id, etc). It prevents us from needing to perform costly run-time reflection in nearly all cases.

This means we're cloning a new event from and event template for every hook called. We can drop these allocations by implementing a custom serializer that writes properties directly from the event template.

Not in scope for this issue, but worth keeping top of mind, is that we can cut Event allocations almost entirely by reusing events. We only need enough events to fill the buffer in the file stream. Once they're written, we can place them back in the pool to be picked up by another thread.

首先定位克隆事件模板的 hook 路径，以及写入事件的 serializer。跟踪静态属性如何从模板传递到每个克隆的事件中。完成的标准是：自定义 serializer 直接从模板写入这些属性，并避免每个 hook 的克隆分配；该 issue 没有提供具体文件或要运行的测试。