@bot build-tsan

Remove debug print

Remove dead pagination code, fix clippy

Superseded by D18958

In D19007#433040, @aimal wrote:

Maybe mention that it's open source.

There is no point adding a mempool view that doesn't show the mempool. The explorer is a source of trust that we send to users and business to check their node is working, you can explain tons of questions within seconds because users nodes will not show the same as the explorer.
Also:

• This will break the testnet explorer
• This is trying to fit cubes into circle holes with finalization. Rather than copying what other chain without preconsensus do, let's take advantage of it to show a better representation. Here is my proposal:
  • Have a view with 2 sides, non final and final
  • Move the tx from one side the other upon finalization This will be useful if e.g. the mempool is full to see what transaction are being finalized and which are pending. Also helps figuring out how block mining works by draining the finalized txs

We have a keepalive already, and websocket has pings which seems a better/cleaner option

Indeed. However, when an app is backgrounded, the websocket nevertheless disconnects, and it does not automatically reconnect when the app is unbackgrounded. This would be nice to handle in chronik-client but I'm not sure how to listen for this event in chronik-client, or if it's even practical to do so there, as the whole backgrounded event is a mobile app thing. I don't think we want capacitor as a dep in chronik-client.

Rebase