nymkappa

Fixes https://github.com/mempool/mempool/issues/2276 [This](https://github.com/mempool/mempool/blob/e48eab403ca06f178f8b4ff6c2d620ad0a661e51/backend/src/tasks/lightning/network-sync.service.ts#L111) is obviously not supposed to be here so I must have added it by mistake

* [x] When the zoom level is high, draw nodes on top of channels and the circle bigger so it's easier to click on it https://github.com/mempool/mempool/pull/2274 * [ ] Show...

I probably have a leak somewhere in my new LN backend code so I need to investigate, easy to reproduce locally, I just need to let the backend run for...

Fixes https://github.com/mempool/mempool/issues/2257 Fixes https://github.com/mempool/mempool/issues/2245 Untested yet, also I will need to update a bit how to read the json if the topology script output .json file directly.

I would request is to modify the topology script to save files with a certain file extension like .topology and then scan for *.topology files to avoid this crash: ```...

``` /Users/nymkappa/Documents/mempool/backend/dist/rpc-api/jsonrpc.js:128 err = new Error(decodedResponse.error.message || ''); ^ Error: JSON integer out of range at /Users/nymkappa/Documents/mempool/backend/dist/rpc-api/jsonrpc.js:128:35 at Array.forEach () at IncomingMessage. (/Users/nymkappa/Documents/mempool/backend/dist/rpc-api/jsonrpc.js:125:25) at IncomingMessage.emit (node:events:539:35) at endReadableNT (node:internal/streams/readable:1345:12) at...

If the topology script is updated with the json export, we can get rid of the XML parser.

Linux:  Android: Looks thicker  Mac: Looks thicker and rounder 

For example, split `176.28.11.68:9760,nzslu33ecbokyn32teza2peiiiuye43ftom7jvnuhsxdbg3vhw7w3aqd.onion:9760` into two rows into a new `nodes_sockets` table, and tag their type (ipv4, ipv6, tor, and so on)

The table is insanely big and that's not gonna work for RPIs if they indexed all blocks