v3.32.4

Fixes status-notifier webhook deliveries that failed when the payload contained non-ASCII characters.

What's Changed

fix(status-notifier): encode the webhook POST body as UTF-8 (#1473) — the status-notifier
built its outbound request with StringEntity(data), which defaults to ISO-8859-1 on Apache
HttpClient 4.5.x. When a workflow/task payload contained a non-ASCII character (e.g. an en dash
– or a non-breaking space), the Content-Length header was computed from the ISO-8859-1 byte
count and disagreed with the actual UTF-8 body, so strict/WAF-fronted receivers rejected the
delivery. The body is now sent as application/json; charset=UTF-8 so Content-Length matches
and notifications deliver reliably. Thanks @shaileshpadave. (Fixes #1399)

Full Changelog: v3.32.3...v3.32.4