[deepratna-awale]

Stacked on #1796. This branch includes #1796's two commits; only the last commit ("Stop logging unhandled ComfyUI websocket messages at Warn") is new here. Once #1796 merges, this PR's diff will show only that commit.

Summary

Follow-up to #1796 for #1790. It addresses what is likely the main source of the log volume reported there.

ComfyClient.HandleTextMessage only acts on executing, status, progress and execution_error. Every other websocket message fell through to:

Logger.Warn($"Unknown message type {json.Type} ({json.Data}), skipping");

That wrote the full pretty-printed JSON payload to app.log at Warn, so no log level setting could hide it. This affected normal ComfyUI traffic (execution_start, execution_cached, executed, execution_success, progress_state) and custom-node broadcasts such as resource monitors that send a message every second. progress_state lists every node in the workflow, so one generation of a large workflow could add thousands of lines.

Changes

• Added ExecutionSuccess, ExecutionInterrupted and ProgressState to ComfyWebSocketResponseType.
• Standard ComfyUI message types the client doesn't use are now skipped silently.
• Any other type, e.g. custom-node broadcasts, is logged at Trace with only its type. The full message is still available at Trace from the existing Received json message line.
• Invalid JSON is still logged at Warn.
• HandleTextMessage is now internal so it can be tested (Core already has InternalsVisibleTo for the test project).

Testing

• New ComfyClientMessageLoggingTests covers each standard type and a custom-node type logging nothing above Trace, the custom type logging its type without the payload, invalid JSON still warning, and the new enum values deserializing. On the previous code, 8 of these tests fail.
• Replayed one 20-step generation plus 60 seconds of monitor messages (84 messages) through the app's logging setup. Before: 84 Warn entries and 468 lines in app.log. After: none.
• Full test suite: the only failures are the network-dependent PackageLinkTests (TestLicenseUrl / TestPreviewImageUri), which couldn't reach the internet in my test environment and are unrelated.