[BUG][NOWEB] - send me.pushName field in WORKING "session.status" webhook event after first scan QR

[AliSot2000]

Describe the bug

The returned Response once the Session is in the State WORKING doesn't contain the me.pushName field despite it being required.

Version

{
  "version": "2024.6.8",
  "engine": "NOWEB",
  "tier": "PLUS",
  "browser": "/usr/bin/chromium"
}

To Reproduce Steps to reproduce the behavior:

1. Start the Docker container AND have a webserver ready to receive the webhooks for session.status
2. Create a Session
3. Scan the QR Code
4. Observe the me.pushName Field is missing in the event for the session reaching the state WORKING

Example JSON I received:

{
    "event": "session.status", 
    "session": "default", 
    "me": {
        "id": "11111111111@c.us"
    }, 
    "payload": {
        "name": "default", 
        "status": "WORKING"
    }, 
    "engine": "NOWEB", 
    "environment": {
        "version": "2024.6.8", 
        "engine": "NOWEB", 
        "tier": "PLUS", 
        "browser": "/usr/bin/chromium"
    }
}

Expected behavior The me.pushName is populated also for the WORKING Event.

[devlikepro]

It happens when you scan qr code for the first time, after that the webhook will have all fields. We'll find the right solution for that, thank you for such detailed issue!

Consider getting session details with GET /api/sessions/{name}/ after you got the first WOKRING event for now