fix: nano-contract history pagination and list order

[alexruzenhack]

Acceptance Criteria

• It should fix nano contract transaction loading for newer transactions
• Add 'Load More' in the footer of transactions list, which triggers the request for older transactions when pressed
  • Hides the 'Load More' button when the last transaction of the list is the 'initialize'

Loading newer transactions

fix-nc-tx-details-loading-logic.mp4

Loading older transactions

nc-load-more-older-txs.mp4

The video above shows a list of transactions initialized with the newest transaction only. When the button 'Load More' is pressed a list of older transactions is loaded. The button 'Load More' didn't show after load because the list has reached its end.

---

Related issues:

• Refactor fetch history to allow concurrency while mounting hydrating the transaction list #514

---

Security Checklist

• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.

[alexruzenhack]

I missed this in the add component PR, but can you rename this component? It doesn't make sense to have a NewHathorButton, how is it different from the HathorButton? Can we merge both?
-- Comment by @andreabadesso on #515, which is now incorporated here.

I will open a KTLO for this.

See issue #527.