`dapr invoke` appends its success banner to stdout after the response body, corrupting piped output

[Mukuwul]

Expected Behavior

stdout of dapr invoke carries only the app's response payload, so piping works (dapr invoke ... | jq); status and progress messages go to stderr, consistent with the project policy established in #748.

Actual Behavior

cmd/invoke.go prints the response to stdout and then prints ✅ App invoked successfully — also to stdout, immediately after the payload (cmd/invoke.go#L88-L91). Piping the response into any parser fails:

$ dapr invoke --app-id myapp --method getstate | jq .
{ ...valid json... }
✅  App invoked successfully      ← jq: parse error

The Unix-domain-socket preview warning has the same problem (cmd/invoke.go#L77), as do the equivalent banner and warning in dapr publish (cmd/publish.go#L95, cmd/publish.go#L76).

Steps to Reproduce the Problem

1. dapr run --app-id myapp -- <any app exposing a method that returns JSON>
2. dapr invoke --app-id myapp --method <method> | jq .
3. jq fails to parse because the success banner is appended to the payload on stdout.

I have a fix ready and will open a PR right after filing this.

Release Note

RELEASE NOTE: FIX dapr invoke and dapr publish status messages now go to stderr, keeping stdout clean for the response payload.

[Mukuwul]

Fix is up in PR #1672 — moves the invoke/publish success banners and UDS preview warnings to stderr; stdout now carries only the response payload. Existing e2e assertions are unaffected (test spawner uses CombinedOutput).