MONITOR: Link DbusConnection and sbus_connection

Although related, the DbusConnection and its associated sbus_connection
had no link in the logs. We had this:

```
[sbus_server_new_connection] (0x0200): Adding connection 0x11fe700.
...
[sbus_server_bus_hello] (0x4000): Assigning unique name :1.3 to connection 0x11e4a90
```

Now we have:
```
[sbus_server_new_connection] (0x0200): New dbus connection 0x11fe700.
...
[sbus_server_new_connection] (0x0200): Adding sbus connection 0x11e4a90.
...
[sbus_server_bus_hello] (0x4000): Assigning unique name :1.3 to connection 0x11e4a90
```

Which allows to establish the relationship between them: the new
sbus connection is associated to the preceding dbus connection. Both
messages are logged by the same function.

Reviewed-by: Alexey Tikhonov <[email protected]>
Reviewed-by: Pavel Březina <[email protected]>

src/sbus/server/sbus_server.c

@@ -405,7 +405,7 @@ sbus_server_new_connection(DBusServer *dbus_server,
 
     sbus_server = talloc_get_type(data, struct sbus_server);
 
-    DEBUG(SSSDBG_FUNC_DATA, "Adding connection %p.\n", dbus_conn);
+    DEBUG(SSSDBG_FUNC_DATA, "New dbus connection %p.\n", dbus_conn);
 
     /* First, add a message filter that will take care of routing messages
      * between connections. */
@@ -429,6 +429,7 @@ sbus_server_new_connection(DBusServer *dbus_server,
         dbus_connection_close(dbus_conn);
         return;
     }
+    DEBUG(SSSDBG_FUNC_DATA, "Adding sbus connection %p.\n", sbus_conn);
 
     dbret = dbus_connection_set_data(dbus_conn, sbus_server->data_slot,
                                      sbus_conn, NULL);