feat: Implement switching to next/previous block on detail pages

[janmichek]

Description

resolves #375
fixes #406

compared to the visual material, the design is old for consistency and will be improved here #148

Demo

firefox_pMVLrk9NPG.mp4

Checklist:

• I have read and followed the Contributing Guide
• add navigation through keyblock detail

[github-actions]

Deployed to https://pr-395-aescan.stg.aepps.com

[michele-franchi]

It looks good but is there a way to disable the next arrow if the keyblock is the last one to avoid the "Requested keyblock has never been seen in the network." screen?

[lukeromanowicz]

I think it should be doable by checking height against blockHeight in recentBlocksStore

[janmichek]

It looks good but is there a way to disable the next arrow if the keyblock is the last one to avoid the "Requested keyblock has never been seen in the network." screen?

Fixed and regenerated the demo

[lukeromanowicz]

I expected that more recent keyblock button will be on the left side since every content we display is always latest first, and older stuff is available when you navigate right. But I guess this works too, just a little bit unexpected.

Overall very good job, I left only one not but I'm afraid it needs to be fixed before merging

[lukeromanowicz]

the button is still clickable, even if it's disabled :/

[janmichek]

Good catch. You are right, haven't spotted this. Fixed

[lukeromanowicz]

Now it works great, thank you for the fix!

[michele-franchi]

It works great!

Could you please open a followup to improve arrows handling and enable again the next one if a new keyblock comes from the websocket? Not super needed right now but this would improve it.