feat(build): output analyze_result.json; fix --device npu config validation

[DingmaomaoBJTU]

Summary

• analyze_result.json: The full static analysis result is now written to the build output folder after every analyze pass (each pass overwrites the previous), so users can inspect node-level compatibility after a build.
• --device npu fix: winml build -m <model> --device npu previously always failed with "quant.task is required". This was a regression introduced in ed7dbfd (fix(build): optional config, autoconf status display, EP compatibility fixes, and perf improvements #477).

Details

analyze_result.json

• analyze_onnx() gains an output_path parameter; when set, it writes AnalysisResult.to_json() to disk after each call
• run_optimize_analyze_loop / _run_analyze_loop thread analyze_output_path through to every analyze_onnx() call
• build/hf.py, build/onnx.py, and the CLI's _run_optimize_stage all supply analyze_result_path

_patch_device regression fix

_patch_device was replacing the entire cfg.quant object with the result of resolve_quant_compile_config(), which only carries weight_type/activation_type. This silently dropped task and model_name that generate_build_config() had already set, causing validation to fail for any device that requires quantization (i.e. NPU).

Fix: when an existing quant config is present, only update the precision fields instead of replacing the whole object.

# Before
cfg.quant = resolved_quant  # drops task, model_name

# After
if resolved_quant is None:
    cfg.quant = None
elif cfg.quant is None:
    cfg.quant = resolved_quant
else:
    cfg.quant.weight_type = resolved_quant.weight_type
    cfg.quant.activation_type = resolved_quant.activation_type