Provide render options to create human-readable config files
Little integration between setup wizard and settings provider

Run the setup wizard only if no user config is detected. Do it by passing a
Bitcoin address from a newly generated EC key pair, which will be stored in the
user config.
Add a `FxExecutor` that provides a executor (and exec context) for FX apps
Add a new setup config element to store OkPAY wallet access data
Make `Wizard` to bind the step pane each time it's active

So the `bindTo()` function may be used to extract data from previous steps.
Introduce a new step in the wizard to retrieve OKPay wallet access data

Using our magic crawler.
Store the OKPay wallet access data into the user config
Remove BitcoinjTest from HandshakeActor tests

This change makes a 3% faster to run the unit tests as there is less
work to do on those tests and they can be run in parallel now.
Remove BitcoinjTest.resetBlockchainBetweenTests

It was unused.
Merge pull request #216 from sortega/fix_it

Fix wrong assertion on OpenOrdersTest
Merge pull request #217 from sortega/optimize_tests

Make UTs 3% faster
Merge pull request #214 from apoloval/task/ThatUserConfig

Integrate OKPay wallet access crawler with Wizard
Move styles from code literals to CSS
Fix settings initialization issue

In `Main` object, if we use the app before launching the wizard, the app keeps
the old configuration instead of the new one generated by the wizard.

Changing the initialization order in `Main` by running the wizard before the
app is initialized (by a lazy val) fixes the issue.
Merge pull request #219 from apoloval/fix/configInitIssues

Fix settings initialization issue
Remove test button on credentials wizard step
Merge pull request #218 from apoloval/task/ThatUserConfig

Move styles from code literals to CSS
Merge pull request #220 from sortega/issue/54_remove_button

Remove test button on credentials wizard step
Fix a bug that caused config entries to be wrongly filtered

When settings or config are saved, the config entries that don't differ
respect the reference ones should be dropped away and not be persisted. There
is a bug that caused some entries not to be correctly filtered.
Remove warning on OkPaySeedTokenRetrievalPane

OkPayProfileExtractor was returning a Future[Option[OkPayProfile]]
and the Success(None) was not considered. As this case is also a 
failure, the warning is removed by simplifying the type to jus
Future[OkPayProfile].