fix: Fix QA issues

[pedroferreira1]

Context

After @tuliomir ran the QA, 3 issues were found. They are described here.

1. The bug in the Transactions list affected all lists, and the cause was that the componentDidUpdate was not triggered when the query parameters changed. I decided to refactor the component to a functional component because this would be done in the future anyway, so I fixed the issue and did the refactor.
2. This issue affected all Token Detail screens of NFTs. The fix was simple (@tuliomir had already done it) and was just the correct way of setting the state.
3. This one was caused by a difference in the way we are passing the parameters data to the Network component right now. this.props had match: { peerId: undefined }, so I had to fix the destructuring, so it could correctly get the peerId information.

Note: While refactoring the Transactions component I found a bug that is affecting the mainnet-production explorer. When the user clicks the 'Previous' button in the list, the API returns the data in the reverse order, so we must reverse the data when this happens. In the middle of the refactor, I also fixed it.

Note 2: I also found a new bug in the Network screen. The 'Reload data' button was not working because it stopped binding the this after the upgrades.

Acceptance Criteria

• Refactor Transactions component to a functional component fixing the bug when the update was not being triggered when the query params changed.
• Fix order of data when user clicked the 'Previous' button in lists that used the Transactions component.
• Fix Token Detail screen when the token is an NFT correctly setting the state of metadata.
• Fix Network screen correctly getting the peerId query param.
• Fix Network screen Reload data button.

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.

[r4mmer]

suggestion(non-blocking): Maybe we should change how PaginationURL works.

The PaginationURL use obtainQueryParams to get the params specified in the contructor from the window.location.search, so maybe we should have a way to get ts, hash and page whenever location changes that is more in line with how function components work.

This obviously is outside the scope of this PR, so maybe we should open an issue for this discussion.

[pedroferreira1]

I agree that it should be different from what it is nowadays. Maybe we could have an event thrown when parameters change. I will create an issue to discuss that, the idea of this PR is just to refactor the component to fix the bugs found.

[pedroferreira1]

#328

[r4mmer]

question(if-minor): why not useState?

I like the use of useMemo, but this seems like a useState without a setter, since this does not seem like a memoization and more like a singleton helper to calculate pagination params.
Something like: const [pagination, _] = useState(...)

[pedroferreira1]

Make sense, done 05f8424

[alexruzenhack]

[question] Is this unmounting really working? I'm asking this because React has probably a bug when dealing with unmounting when more then 1 useEffect is declared in the component. If it is working, all good, otherwise I would solve this issue by declaring this useEffect first.

[pedroferreira1]

I tested and it's working fine when the screen is unmounted. What's this bug that React has with more than one useEffect?

[alexruzenhack]

Maybe this is a thing of React Native. When we use two useEffect with unmounting callbacks only the the first unmounting callback from the first useEffect is called, never the second. This case is little different because the first useEffect didn't register an unmounting, maybe you can make this test latter. However, for this PR it is enough. I'm approving.