Add infoHash to the logs when a duplicate torrent is added

[AN1MATEK]

Suggestion

Sometimes people upload to private trackers without creating a new infoHash for the torrent, which prevents cross-seeding. After discussion in #20323 it was decided that this is not going to be worked around - that's ok.

However the logs do not show precise information on which torrent is duplicated - it just shows the name, which can be the same for many torrents. A first fix would be to include the infoHash in the logs. That should be easy enough to implement.

On top of that, I would like to suggest a GUI pop-up when the torrent fails to add because of this issue. As right now, the UI gives no information that the torrent did not add, let alone why.

Use case

Identify exactly which torrent is the "duplicate"

Extra info/examples/attachments

Example from the CLI as 5.0.3
(N) 2025-01-08T12:25:20 - Detected an attempt to add a duplicate torrent. Existing torrent: Movie.1969.BluRay.REMUX.AVC.DTS-HD.MA.5.1-Group. Result: Merging of trackers is disabled

Possible solution
(N) 2025-01-08T12:25:20 - Detected an attempt to add a duplicate torrent. Existing torrent name: Movie.1969.BluRay.REMUX.AVC.DTS-HD.MA.5.1-Group. Existing torrent infoHash: xxxxxxxxxxxxxxxxxx. Result: Merging of trackers is disabled