[transfer-engine] Update transfer notification icon

Make sure transfer engine stop if booster goes away.

[systemd] Require booster-qt5.
Signed-off-by: Marko Saukko <marko.saukko@jolla.com>

Boosting

[boosting] Use qt5 booster instead of generic one.
[dbus] Systemd file for dbus service so we get dependencies set.
Signed-off-by: Marko Saukko <marko.saukko@jolla.com>

[packaging] Drop qt4 packaging.
Signed-off-by: Marko Saukko <marko.saukko@jolla.com>

Finish activity prior to firing the statusChanged event

It guarantees that the process will exit after 5 sec of inactivity.

createDownload() and createSync() calls don't need to explicitely reset the
timer because they always fire the statusChanged() signal which is wired to
exitSafely()

If TransferEnginePrivate::exitSafely() finds out that activity is still
ongoing it should cancel previously sheduled delayedExitSafely() call.
Otherwise delayedExitSafely() may be invoked between two syncs causing
nemo-transfer-engine to exit and get immediately restarted by D-Bus which
isn't something we really want. We want to exit when all the activity has
really calmed down.

The statusChanged() event is wired to TransferEnginePrivate::exitSafely()
which would otherwise think that something is still going on and wouldn't
exit, so transfer engine would keep on running forever. Which is what it
currently does.

Fix memory leaks

[transfer-engine] Better attemp at fixing the QSqlDatabase leak

[transfer-engine] Fix QSqlDatabase leak.

We need to remove the database from the list of connections in order to really close
the database and cleanup any temporary files left.

[transfer-engine] Updated example share plugin to use translations.

Removed empty lines.

Removed references to files, which are not in git.

Added correct URL in spec file.

Removed autosaved file.

Changed licence information

When transferring multiple files via Bluetooth, we quickly receive
one transfer request after another, so this causes a timing issue
where the engine may quit immediately after the first request and
is in the process of closing down when the next request is received,
and thus cannot be started again for the next request.

[nemo-transfer-engine] Now title or description is actually stored to the database.

[transfer-engine] Fix to account and share method list handling.

Review fixes

[nemo-transfer-engine] Use invoker to launch transfer engine

Previously, the transfer engine wasn't invoked, but instead launched
directly.  This means that it would not have privileges.