* Show parity/light.js's logs too

* Remove txCount from withAccount

* withBalance shows component immeidately

* Play around

* Make it work

* Cleaner code

* Remove 'Loading account tokens...' modal

* Re-order import

* Optimize code

* Fix regression

* Fix typo

* Luke's grumbles

* Put "checking..." when fetching async values

* Show gas error on amount field

* Parity Ethereum bundling

* Grumbles; update light.js

* Grumbles

* Merge in PR#394 ac-upd-post: refactor sendStore post/postRaw

* Download highest version matching requirement rather than latest beta

* Rename RequireVersion to RequireParityVersion

* Grumbles

* Change Parity version requirement to ~2.4.1

* Fix --no-run-parity with Parity already running

* Grumble

Co-Authored-By: axelchalon <[email protected]>

* Change health states to node-internet, node, and sync

* Change from using STATUS symbol states to using a status object that contains the different states with their status

* Show chain name and percentage in modals too

Summary of actions performed:

* App.js routes
	* AccountsList
		* New functionality - `<RequireHealthOverlay require='connected-offline'>`
			* Note: we need to be connected even for the AccountsList page since most accounts actually come from parity-ethereum (as pointed out by @amaurymartiny). New functionality (@amaurymartiny proposal) uses additional 'connected-offline' state so if we are connected to the node but not to the internet we can show the AccountsList page
	* Accounts (token list page)
		* Retain existing functionality - `<RequireHealthOverlay require='sync'>`
	* Create Account / Import Account
		* New functionality - `<RequireHealthOverlay require='connected-offline'>`
	* Backup Account
		* New functionality - `<RequireHealthOverlay require='connected-offline'>`
	* Onboarding
		* New functionality - no overlay since not wrapping App.js
	* Search tokens (Whitelist)
		* Retain existing functionality - `<RequireHealthOverlay require='sync'>`
* Send.js routes
	* TxForm, Unlock, TxQrCode, ScanSignedTx, SignedTxSummary
		* Retain existing functionality - `<RequireHealthOverlay require='sync'>`
	* Sent
		* Retain existing functionality by wrapping the individual component instead of App.js with: `<RequireHealthOverlay require='connected' fullscreen>`

* Note: `RequireHealthOverlay` has two states:
		* `require='connected-offline` no alert/overlay when user connected to a local node but not connected to the internet
		* `require='connected'` shows full screen alert when the user is not connected to the node and and not connected to the internet
		* `require='sync'` shows when the user is not sync
* Note: Only the Sent component has a fullscreen overlay
* Note: This wraps everything related to eth/token/balance/transfer with `require='sync'`
* Note: We are not wrapping App.js anymore since when using both `<RequireHealthOverlay require='connected' fullscreen>` in addition to wrapping other components such as Accounts.js with `<RequireHealthOverlay require='connected-offline'>` doesn't allow it. Instead just wrap individual components

review-fix: Remove value from To since already initialValue. Modify existing initialValue for Amount

review-fix: Use react-final-form field to connect to state. Change from defaultValue to value to overcome warning

fix: Fix SignedTxSummary page for Parity Signer tx so it shows amount field similar to on Unlock summary for non-Signer tx

* Remove `decimals`, `onClick`, and `tokens` props from TokenAddress as was only required
on TokenBalance

* Update SignedTxSummary so "To" input field is above "Amount"

* Explicitely pass down `drawers` prop since it is used by Card component

* Remove incorrect `handleClick` from TokenAddress component, as
that was functionality from TokenBalance

* Add `isEstimatingTxFee` so we can check if all values including `gas` are available
without actually having to calculate the tx fee and incorporate into estimateTxFee method

* Display and disable the "Checking..." button if the `isEstimatingTxFee` returns false (i.e. `gas`
still undefined)

* Note: The bug associated with #361 appears to be Parity Signer-specific. If the user can click "Scan" before the `gas` has been calculated, then when it tries to go to the paritytech/fether/packages/fether-react/src/Send/TxQrCode/TxQrCode.js, where it calls `getRlp()` to get the value for the rlp prop of the QrSigner component, which calls `transactionToRlp(this.tx)` to get the RLP of the unsigned tx that is provided as an argument paritytech/fether/packages/fether-react/src/stores/sendStore.js, it crashes if `this.tx` contains a `gas` property that's undefined.
So we need to prevent the user from being able to click "Scan" before the `gas` property has been determined.
We do this by disabling the button and displaying "Checking..." until `isEstimatingTxFee` returns true, and only then
do we display "Scan" and enable the button

for good measure

* Remove titleOffset and add placeholder width for header nav buttons

* Remove passing `screen` prop for specific pages

* Change Account screen so its header uses the Information component with a big identicon, a short address,
so it is clickable, and with identicon on left of name and address.

* Apply extra bottom margin between name and account address when Information component used in the header

* Update header so it uses Flexbox according to docs as intended

* Since we're using Flexbox without placeholder spacing for the left and right header buttons, when the title
is shown in the header it is offset if there is only a left or right button. So a `titleOffset` prop
is used on pages where the Header component is used to indicate if the title needs to be offset to the left
or right so it appears centered in the screen. We also pass a `screen` prop (named after the component where the
Header component is being used so we can tailor the header spacing on specific screens.

* Re-order props alphabetically

* QUESTION - should we consider always adding placeholder spacing for where both right and left buttons in header would be as an alternative so no offset for the title is require?