Loading screen with the logic of setting up an identity account

[katszwn]

Description

TODO:

• tests
• create identity
• IPFS
• Ethereum integration

Fixes #966

What does it solve?
Added container for loading, set up middleware which injects Jolocom Lib in actions, hooked up generate keys functionality to the loading component.

Were there any particular challenges that you faced and/or things that were not straightforward?

• iOS development flow, also wrote custom middleware which was conflicting with later added Thunk middleware - in the end used thunk.withExtraArgument()
• conflicting utf8 packages react native in version 0.52 had a util for utf8 conversion and it was overriding npm package (utf8.decode() is not a function error mathiasbynens/utf8.js#17) - upgraded React Native to the latest version fixed the issue
• had to upgrade Haul because of the issue I was getting on Android Unexpected keyword 'const'. Const declarations are not supported in strict mode callstack/haul#400. I was still getting the same error, but related to jolocom lib later

CURRENT BLOCKERS:

• IPFS library is not working, probably due to how it's making HTTP requests - it's probably incompatible with how React Native makes HTTP requests, which doesn't support streams, binary data by default. NEXT STEPS: try out different IPFS libraries, or make requests manually using react native HTTP API, perhaps use https://github.com/joltup/react-native-fetch-blob
• there was an issue with ES6 syntax in the jolocom-lib. Turned out the library was transpiled in a wrong way, but that exposed another issue on iOS, which was previously (before re-transpiling and updating ReactNative) running past the identity creation - Use Object.defineProperties instead of Object.assign jolocom-lib#50, the WIP solution is pushed to the corresponding branch, JSON parsing is broken. Perhaps it's worth doing further research on the cause of this issue and the Android issue - perhaps we should also use ts-loader next to babel-loader

What should others know about the solution?
Backend Middleware should be used to inject agents and external libraries that needs initializing

Is this change going to break other dependent services?
No

Checklist

• Keep flags added to the PR up to date
• Make sure the title describes the code well, description should contain Fixes #number_of_an_issue and a brief decscription of changes
• Make sure the PR is readable and contains changes only related to a single issue. Otherwise - divide into separate PRs
• Add a screenshot if there were any UI changes involved
• Add new tests and make sure all tests are passing
• Make sure all edge cases are taken into account and covered by tests
• Run linter and fix all the errors and warnings

[Exulansis]

This is ready for merging, there is one issue with Snyk, but I do not have the privileges to see it for some reason :D Once that is solved, we can proceed.

I will create a new branch for implementing a generic error screen, and then complete the error handling on this branch.