fixes for #189:
  - Change background color to faint blue
  - Add 3px blue line on the left

This method actually guarantees that the result is a nonempty string,
so there is no need to expose an Option.

 * serde: 1.0.42

If we remove the button to load more, we need to show always the
vertical scrollbar to receive the edge-reached event.

There's a accesibility problem here, because I've not been able to
launch this event without the mouse wheel so currently there's no way to
load more with the keyboard or only the mouse without the wheel, as far
as I now.

Fix #48

Fix #182

This adds a condition to print the new message divider so that it
is not shown for messages send by the user.

See #133

There's depenedencies between ui files, so we need to load in the
correct way.

Since 2394670b all builds on the CI have
been failing. I believe this is the issue.

Fix #185

Both items and collections accessed through secret service API might be
locked. Secrets of locked items cannot be accessed. Locked collection
cannot be modified.

Implement unlocking as recommended by secret service API specification:

* The client application should act as if it must unlock each item
  individually.
* A client application should always be ready to unlock the items for
  the secrets it needs, or objects it must modify.
* It must not assume that an item is already unlocked for whatever
  reason.

Fixes issue #175.

New features:
 * Add new description to README, and some other small README improvements
 * new autoscroll with animation
 * Ability to launch multiple Fractal instances using FRACTAL_ID env

Fixes:
 * Escape text in body using the last html2pango
 * center inapp notification
 * Fix request with no timeout
 * Show user id when the displayname isn't present
 * Fix macos compilation problem with notify_rust
 * autocomplete: fix change usernames font color to white when selection ends at the same position as the username
 * Avoid destroy dialog on Esc

This patch moves the password and token store to a different module and
let the trait methods clean. Using this as a base it's possible to
implement other password storage modules and add some logic in the trait
to choose which method to use. So we can use an environment variable or
gsettings to choose an insecure password storage, like a file in cache
directory or maybe use other password storage implementations.

This is a first step to split app.rs in different files.

I've implemented as a trait because this was the easier way, with this
change we don't need to change anything in the app.rs because this trait
adds the needed methods to the struct.

I want to add other password storage methods, for the people that
doesn't have secret-service, maybe configurable as a gsettings.

reqwest use a default timeout of 30 seconds, so for no timeout we need
to provide a timeout of None.

https://docs.rs/reqwest/0.8.5/reqwest/struct.ClientBuilder.html#method.timeout

This should fix #171