Rework zone profiler to include event processing

[Endaris]

The zone profiler currently excludes input events from profiling.
Input events can unpredictably change state (like exiting the game) which can require some extra handling on write or on quit, as otherwise the data may end up corrupt.
Until recently there was no code that called the profiler as a direct result of input handling so there was no issue.

The newly added puzzle editor very much does that though which causes a crash because the frame is not initialized yet when the profiler is called to document the match start.