Coded new fragment appearance

Domain, name and description come from provider.json

Next step: code buttons to login or to use anonymously.
Use anonymously from ProviderDetail works OK.

Tested with dev.bitmask.net, I use the previously downloaded certificate
(I should not do that, I'll file an issue because I should download it
once the user has requested to do so).

Next step: login button from ProviderDetailFragment.
Login button from ProviderDetailFragment works.

I return an intent with ConfigHelper.LOG_IN extra present. Dashboard
looks for it, and if found, starts LogInDialog.
Removed unnecessary toasts.

They are commented, just in case we decide to include any of them before
releasing 0.2.0.
JSONExceptions from ProviderDetail returns false.

Buttons from this fragment are shown if the key is present and contains
a "true" value, but if an exception occurs the button it's not showed.