chore : Reduce CoreTrace analyzer orchestration logs and only show per-file progress in verbose mode

[SizzleUnrlsd]

Problem

Running CoreTrace in normal mode currently emits a large amount of informational output from the orchestration layer, especially one Processing file: ... line per source file.

On large codebases, this creates a lot of noise and makes real analysis results harder to read.

This is particularly visible when invoking the stack analyzer on many files: the default output includes setup logs and a per-file progress stream even when --verbose is not enabled.

Current behavior

Examples of noisy default logs:

• Initializing ToolInvoker...
• Using standardIO for IPC.
• Processing file: ... repeated for every input file

Expected behavior

Default mode

Keep output concise and summary-oriented:

• analysis start
• selected tool(s)
• file count / phase count
• warnings and errors

Verbose mode

Enable detailed operational logs:

• per-file processing
• ToolInvoker setup details
• IPC backend details
• any other high-cardinality execution traces

Quiet mode

Keep current quiet semantics and suppress non-essential progress logs.

Proposal

Introduce a clearer logging policy for the orchestration layer:

• Info: high-level summary events only
• Debug: per-file, setup, and execution-detail logs
• Warn / Error: unchanged

Concretely:

• move Processing file: ... logs to Debug
• move ToolInvoker initialization / IPC selection logs to Debug
• keep summary logs such as Running static analysis on N file(s) and Running CoreTrace Stack Analyzer on N file(s) at Info

Why this approach

This preserves debuggability without flooding normal runs.

Architecturally, it also creates a cleaner separation between:

• user-facing progress summaries
• developer-facing execution diagnostics

That makes the CLI easier to use on large projects while keeping full traceability available through --verbose.

Acceptance criteria

• Running CoreTrace without --verbose no longer prints one line per processed file
• Running CoreTrace with --verbose restores detailed per-file progress logs
• Existing warnings and errors remain visible
• --quiet behavior is preserved
• No analyzer functionality changes, only log verbosity policy