Even at track-origins=1, the per-call origin maintenance dominates two
hot helpers used by every QueryLog flush:
  - ProfileEvents::dumpToMapColumn (Interpreters/ProfileEventsExt.cpp)
  - SettingsImpl::dumpToMapColumn  (Core/Settings.cpp, already covered)

Each walks hundreds of keys and does tight LowCardinality::insertData
calls in a loop, so the per-call __msan_set_alloca_origin overhead
adds up to seconds per `SYSTEM FLUSH LOGS query_log` and the failing
tests on the MSan WasmEdge 2/2 shard hit the 180 s flush-wait
timeout. The CI logs show Block phase up to 14.7 s for a 5759-entry
batch, dominated by these two functions.

Extend the existing per-file override added in ClickHouse#92716 to also cover
ProfileEventsExt.cpp and SystemLog.cpp. These files are leaf helpers
where MSan checks don't carry uninit values into user code, so
turning origin tracking off here is safe; the rest of the build keeps
origin tracking.

Even at track-origins=1, the per-call origin maintenance dominates two
hot helpers used by every QueryLog flush:
  - ProfileEvents::dumpToMapColumn (Interpreters/ProfileEventsExt.cpp)
  - SettingsImpl::dumpToMapColumn  (Core/Settings.cpp, already covered)

Each walks hundreds of keys and does tight LowCardinality::insertData
calls in a loop, so the per-call __msan_set_alloca_origin overhead
adds up to seconds per `SYSTEM FLUSH LOGS query_log` and the failing
tests on the MSan WasmEdge 2/2 shard hit the 180 s flush-wait
timeout. The CI logs show Block phase up to 14.7 s for a 5759-entry
batch, dominated by these two functions.

Extend the existing per-file override added in #92716 to also cover
ProfileEventsExt.cpp and SystemLog.cpp. These files are leaf helpers
where MSan checks don't carry uninit values into user code, so
turning origin tracking off here is safe; the rest of the build keeps
origin tracking.

The earlier override on Settings.cpp / ProfileEventsExt.cpp /
SystemLog.cpp removed __msan_chain_origin / __msan_set_alloca_origin
from the helpers (dumpToMapColumn, flushImpl). But the per-row
LogElement::appendToBlock functions, which are called once per row
inside flushImpl and dominate the Block phase, were still being
compiled with origin tracking at level 1. With ~5000 rows per
query_log flush, the per-call origin-tracking overhead in those
functions added seconds to every SYSTEM FLUSH LOGS query_log.

Cover QueryLog.cpp, QueryThreadLog.cpp, MetricLog.cpp,
QueryMetricLog.cpp. Result on the rebuilt MSan binary:
  QueryLogElement::appendToBlock     57 KB -> 39 KB (-32%), 0 origin calls
  QueryThreadLogElement              9.5 KB -> 6 KB (-37%), 0 origin calls
  MetricLogElement / QueryMetricLog        also 0 origin calls
Compare with PartLogElement::appendToBlock (still origin-tracked):
55 __msan_set_alloca_origin calls in 22 KB.

Also drop the `-fomit-frame-pointer -momit-leaf-frame-pointer` flags
from the override: they were an artifact of exploratory commits in
PR #92716 that didn't move the needle (azat/Algunenano review thread
on Core/Settings.cpp). The single-line override on Common/ThreadFuzzer.cpp
keeps them with a comment pointing at commit d5825ec, where they
were measured to almost double ThreadFuzzer test throughput.