Add push notification trace UUID tracking for debugging

[jirkah]

Summary

This change adds support for tracking push notifications through a trace UUID, enabling better debugging and tracing of push notification flows across the system.

Key Changes

• Added push_trace_uuid parameter to the push notification workflow:

  • Added as optional parameter to send_push_notification() method with default empty string
  • Extracted from incoming bus events via WAZO_PUSH_TRACE_UUID field
  • Included in push notification payloads sent to the bus

• Enhanced logging throughout the push notification lifecycle:

  • Log push trace UUID when sending push notifications in services.py
  • Log push trace UUID when cancelling push notifications in services.py
  • Log push trace UUID when publishing events in notifier.py (both send and cancel operations)
  • Log push trace UUID in bus consumer when receiving push notification requests

• Updated test coverage:

  • Added WAZO_PUSH_TRACE_UUID to test event data
  • Updated test assertions to verify trace UUID is passed through the call chain

Implementation Details

• The trace UUID is optional and defaults to an empty string for backward compatibility
• Logging includes the trace UUID alongside user UUID and call ID for correlation
• The trace UUID flows through the entire push notification pipeline: bus consumer → service → notifier → bus producer

https://claude.ai/code/session_0193K1vomcUqeAw3TAif3MCK

---

Note

Low Risk
Low risk: changes are additive (optional push_trace_uuid field) and primarily affect logging and bus payload metadata for push notifications/cancellation.

Overview
Adds end-to-end propagation of an optional push_trace_uuid for mobile push notifications, extracted from UserEvent (WAZO_PUSH_TRACE_UUID) and included in the payload sent on the bus.

Improves observability by logging the trace UUID when receiving, sending, publishing, and cancelling push notifications, and updates the test_bus_consume assertion to verify the new argument is passed through.

^{Written by Cursor Bugbot for commit 56489ee. This will update automatically on new commits. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wazo-community-zuul]

Build succeeded.
https://zuul.wazo.community/zuul/t/local/buildset/a70b699287fb4e228baa3435f328c2bf

✔️ tox-linters SUCCESS in 3m 03s
✔️ wazo-tox-py311 SUCCESS in 3m 04s
✔️ debian-packaging-bookworm SUCCESS in 2m 55s
✔️ calld-tox-integration SUCCESS in 1h 07m 27s