Fix limited Cryptokitties display and order

[deomaius]

fixes #6839

Summary

Beforehand a limited amount of 20 kitties would appear in the status wallet, I investigated to find that the Cryptokitties API is only limited to 20 collectables per call, which explains why the limited amount was appearing in one's wallet. A parameter of the collectables by wallet call is providing an offset to index items for an individual wallet, so I simply created a range that extended from zero to the number of cats in a said wallet, incrementing by 20. This was then mapped so that it could be fed into http-get-n. Where each individual response was pushed to a sorted array, to finally be loaded simultaneously with one call to load-kitties when all of the ids were obtained.

Unfortunately maintaining an array's order whilst leveraging mapv is not possible, I did find that filterv work effectively in this department but not when applied to http-get-n, it resulted in the following error:

TypeError: cb is not a function. (In 'cb(value)', 'cb' is "TypeError: Network request failed")

Functional

• 1-1 chats
• public chats
• group chats
• wallet / transactions
• dapps / app browsing
• account recovery
• new account
• user profile updates
• networks
• mailservers
• fleet
• bootnodes

Non-functional

• battery performance
• CPU performance / speed of the app
• network consumption

Steps to test

• Open status application
• Navigate to the wallet tab
• Expand a wallet with more than 20 Cryptokitties
• Expand the collectables tab and Select Cryptokitties
• Enjoy the sight of accurate balances

status: WIP

[ghost]

Hey @SamGos, and thank you so much for making your first pull request in status-react! ❤️ Please help us make your experience better by filling out this brief questionnaire https://goo.gl/forms/uWqNcVpVz7OIopXg2

[ghost]

Pull Request Checklist

• Docs: Updated the documentation, if affected
• Docs: Added or updated inline comments explaining intention of the code
• Tests: Ensured that all new UI elements have been assigned accessibility IDs
• Tests: Signaled need for E2E tests with label, if applicable
• Tests: Briefly described what was tested and what platforms were used
• UI: In case of UI changes, ensured that UI matches Figma
• UI: In case of UI changes, requested review from a Core UI designer
• UI: In case of UI changes, included screenshots of implementation

[status-im-auto]

Jenkins Builds

❔	Commit	#️⃣	Finished (UTC)	Duration	Platform	Result
❌	6e24423	#1	2020-01-13 14:50:46	~3 min	ios	📄log
❌	6e24423	#1	2020-01-13 14:51:00	~3 min	android	📄log
❌	6e24423	#1	2020-01-13 14:53:42	~6 min	android-e2e	📄log

[flexsurfer]

#9968