Fix: clients output in JSON should not include logging

[josecelano]

The console clients' output should not include logging info when the output is JSON. IT fixes this behavior:

Command:

$ cargo run --bin udp_tracker_client announce 144.126.245.19:6969 9c38422213e30bff212b30c360d26f9a02136422 
    Finished `dev` profile [optimized + debuginfo] target(s) in 0.09s
     Running `target/debug/udp_tracker_client announce '144.126.245.19:6969' 9c38422213e30bff212b30c360d26f9a02136422`

Output:

```s
2024-06-26T07:46:10.051490Z  INFO torrust_tracker::console::clients::udp::app: logging initialized.
{
  "AnnounceIpv4": {
    "transaction_id": -888840697,
    "announce_interval": 300,
    "leechers": 0,
    "seeders": 1,
    "peers": []
  }
}

The line 2024-06-26T07:46:10.051490Z INFO torrust_tracker::console::clients::udp::app: logging initialized. or any other lines should not be included. I will open a discussion about how to deal with logging in console clients.

[josecelano]

I've opened a discussion about implementing login in the console clients: #920

[josecelano]

ACK 2518c54