[qtcontacts-sqlite] Revert "[qtcontacts-sqlite] Fix: Check for read/write capability using QFileInfo"

This reverts commit 19b030ba6ffeca151729dfc0d5ace47a13027903.

This change caused some processes to fail to gain access to the privileged
database when launched from lipstick, even though the same application
launched from a privileged shell could access the privileged database. The
problem does not affect all users.

Conflicts:
	src/engine/contactsdatabase.cpp
[qtcontacts-sqlite] Aggregate using only nickname where real names are absent

If a contact has a nickname and no other name details, we should find
aggregate matches by exact match of nickname.  This is particularly
relevant for SIM contacts, which have a nickname and no other details
(besides a number).

When creating a local representation of an aggregate, we must also handle
the case where the original contact has no name details, and only a nickname
detail.  In this case, the local must be identified by the nickname, or
it will easily become unidentifiable if detached from its original
aggregate.
Whitespace cleanup
Merge pull request #101 from matthewvogt/aggregate-nicknames

[qtcontacts-sqlite] Aggregate using only nickname where real names are absent
[qtcontacts-sqlite] Switch to user_version for schema management

Sqlite now supports the user_version pragma, which provides a more
flexible mechanism for managing database versioning.
[qtcontacts-sqlite] Index the likely filter columns on Contacts table

The status columns are likely to be used to filter queries over the
primary table.
Merge pull request #103 from matthewvogt/user-version

[qtcontacts-sqlite] Index the likely filter columns on Contacts table
[qtcontacts-sqlite] Remove Qt4 support

After this change, the engine can be built only with qt5 and qtpim.
[qtcontacts-sqlite] Remove QContactIdType typedef

This typedef was only used to mitigate differences between qtpim and
QtMobility Contacts interfaces.
[qtcontacts-sqlite] Remove SKIP_TEST definition

This macro was only used to mitigate differences between qt4 and qt5.
packaging: use _smp_mflags
Merge pull request #104 from matthewvogt/remove-qt4

Remove qt4 support
Update exported version number
[qtcontacts-sqlite] Add limited support for deleted contact change log filtering

Deleted contact IDs can be retrieved via the QContactChangeLogFilter
with eventType set to EventRemoved.  These filters cannot be used for
general queries, or to retrieve QContact details.
Merge pull request #105 from matthewvogt/deletion-log

[qtcontacts-sqlite] Add limited support for deleted contact change log filtering
[qtcontact-sqlite] Allow contacts to be deactivated

Deactivation allows a contact to be removed from the working set, yet
still retain its data and relationships.  If reactivated, the contact
should resume the state it had prior to deactivation.  Deactivation can
only be performed for contacts that have an external sync target.

A contact can be deactivated by saving a detail of type QContactDeactivated,
and reactivated by removing that detail.  A deactivated contact has
the IsDeactivated flag set in QContactStatusFlags.

By default, deactivated contacts are excluded from queries; they can
be explicitly included by matching for the IsDeactivated flag in
QContactStatusFlags.  Retrieving a deactivated contact is also possible
by specifying its contact ID directly.
Merge pull request #106 from matthewvogt/deactivation

[qtcontact-sqlite] Allow contacts to be deactivated
Update exported version number
[qtcontact-sqlite] Return correctly typed date information

Birthday and anniversary details should yield QDate rather than
string representations.
Merge pull request #107 from matthewvogt/date-types

[qtcontact-sqlite] Return correctly typed date information