Exit application when welcome dialog is closed: Bug #713961
Present user with dialog when TLS cert warnings detected: Bug #713247

When a TLS certificate warning is detected, the user will now be
presented with a warning dialog presenting them with three options:
Trust This Server, Always Trust This Server, and Don't Trust This
Server (the default).  The user must select one of the first two
buttons for Geary to continue connecting to the server, otherwise it
will close the Account object for the duration of the application
session.

This patch introduces a dependency on gcr-3, which is used to pin TLS
certificates (i.e. persist the user's choice of ignoring the TLS
warnings).
Updated Hebrew translation
Updated Ukrainian translation
Updated Polish translation
Updated Romanian Translation
New scrolling system for inline composers

The editor in the composer no longer shows its own scrollbar.  Instead,
the conversation view allocates enough space to hold the composer
without any scrolling.  The composer then positions and scrolls itself
to create the illusion that the outer scroll bar controls it.

To track the size of the composer, we put all the text in a div and mark
that as contenteditable.  Then, when the div changes height, we update
the layout.  We use the user_changed_contents signal as a proxy for
this.

https://bugzilla.gnome.org/show_bug.cgi?id=730955
Check for inline compositions before switching conversation from notification

https://bugzilla.gnome.org/show_bug.cgi?id=733430
Check for inline composers before archive or trash

https://bugzilla.gnome.org/show_bug.cgi?id=733340
Don't signal ClientConnection IDLE StatusResponses

This fixes a subtle bug in the IMAP stack.  The most prominent symptom
was for the entire folder list to clear after running Geary for a day
or so.  Smaller symptoms were less noticeable, but could include dropped
incoming messages (which would be picked up later when Geary was restarted
or the connection was dropped and reestablished).

The essential problem is that ClientConnection generates internal
IDLE commands to control data flow and to receive unsolicited
server data.  It would always signal the corresponding IDLE responses
from the server.  These were being stored in the ClientSession object
as "finished commands" for commands it did not issue, leading to the
internal IDLE tag being kept around in a hash map.  When the tag
numbering rolled over (which could take 8 - 12 hours depending on the
connection) the ClientSession would complete new commands with those
leftover tags instantly, causing for results to be dropped and the
session state machine to be out of sync with the server.

The solution is simply not to report status responses for internal
IDLE commands.
Improved debugging and appropriate Error in Imap.Account
Use NORMAL SQLite synchronous mode

With the database improvements over this cycle, testing shows
that we can now switch to NORMAL synchronous mode with little to
no performance loss but better database safety.
Reduce database lags: Bug #725929

This reduces lags by searching for incomplete emails in slices as
well as in separate database transactions.

This is a refinement of commit 6672f8, where the database was
searched in slices but in one transaction.  This didn't completely
solve the db lags in this code path.
Merge NEWS and debian/changelog from geary-0.6 branch
Updated to 0.7.2
Updated Spanish Translation
Updated Indonesian translation
Add French docs translation
Updated Brazilian Portuguese translation
Updated Swedish translation