bug: enabling profiler is clearing registers

[mm-zk]

In some of our use cases, we read the 'result' of the computation from registers 10-17 after computation has finished.

Unfortunately if profiler is enabled, (with diagnostic config) - these registers are getting cleared.

To reproduce - use run_base_system from zk_ee, it will fail if Simulator config from zk_os_runner has diagnostics enabled, and pass if diagnostics are disabled.

[shamatar]

What do you call "enable profiler"? Right now default way of running tests both produces flamegraphs, and gives correct output values