Fix beacon live transaction chain loading

[ghost]

Description

Fix the transaction loading issue in the beacon chain from the first page.

It targets the transaction chain of the current day to retrieve the beacon slots transaction and aggregate them.

Related to #291

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

When a transaction is submitted and stored on the beacon chain, when the next slot is sealed and send through a transaction, when you are refreshing the first page, you should be able to see the transaction and the previous ones.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[ghost]

Current dependencies on this PR:

• Set last transaction address from the genesis in DB #352 *
• Write transaction to specific genesis address #353
• Fix previous_summary from summary timer #354
• Write beacon slot to summary chain #358

[imnik11]

LFTM, live streaming is also being cached along with pagination.