`nimble deps` redundantly repeats the same deps over and over

[arnetheduck]

nora (@0.1.0)
├── nim >= 2.0.12 (@2.2.4)
├── prl_to_pc @any (@0.1.0)
│   └── nim >= 1.6.0 (@2.2.4)
├── seaqt #qt-6.4 (@0.6.4.0)
│   └── nim >= 2.0.0 (@2.2.4)
├── stew @any (@0.4.1)
│   ├── nim >= 1.6.0 (@2.2.4)
│   ├── results @any (@0.5.1)
│   │   └── nim >= 1.2 (@2.2.4)
│   └── unittest2 @any (@0.2.4)
│       └── nim >= 1.6.0 (@2.2.4)
└── web3 >= 0.8.0 (@0.8.0)
    ├── bearssl @any (@0.2.6)
    │   ├── nim >= 1.6.0 (@2.2.4)
    │   └── unittest2 @any (@0.2.4)
    │       └── nim >= 1.6.0 (@2.2.4)
    ├── chronicles @any (@0.12.2)
    │   ├── faststreams >= 0.3.0 (@0.5.0)
    │   │   ├── nim >= 1.6.0 (@2.2.4)
    │   │   ├── stew >= 0.2.0 (@0.4.1)
    │   │   │   ├── nim >= 1.6.0 (@2.2.4)
    │   │   │   ├── results @any (@0.5.1)
    │   │   │   │   └── nim >= 1.2 (@2.2.4)
    │   │   │   └── unittest2 @any (@0.2.4)
    │   │   │       └── nim >= 1.6.0 (@2.2.4)
    │   │   └── unittest2 @any (@0.2.4)
    │   │       └── nim >= 1.6.0 (@2.2.4)

Here we can see two packages depending on stew - both of them redundantly print the transitive deps of stew which are always the same - instead, it could just print ... for the second appearance - as is, the list easily become thousands of lines long for even moderate projects - the above package for example, even though the number of unique packages it depends on is limited, fills several screenfuls with repeated deps.