Pass account wrapper object to storage code

The Tp object path is insufficient for non-sparql implmentation.
Add option to update telepathy contacts via QtContacts API

To select the QtContacts API writer, alter the DEFINES in:
  plugins/telepathy/telepathy.pro
[contactsd] Adapt to aggregated self contacts
[contactsd] Allow backend to perform phone number normalization
[contactsd] Remove unwanted extra aggregate of self contact
[contactsd] Update customLabel if possible
[contactsd] Do not overwite account after status updates
[contactsd] Support batched contact operations

Fetching contacts in large batches is much more efficient; it takes less
than twice as long to fetch an order of magnitude more contacts, it seems.

OTOH, writing contacts in batches does not produce noticeable time
reductions, although it will reduce the number of change signals
generated, and thus subsequent queries from other parties.
[contactsd] Use small batches for updates

Large batches will block writes for too long, but small batches should
yield better overall performance.
[contactsd] Preserve existing behavior in removeBuddies

There was no need to alter the OfflineRosterBuffer behavior due to
failure of accountWrapper lookup.
[contactsd] Remove batch contact removal code

Performance of contact group removal is not very significant; simplify
the code by removing the unused, (presumably) optimized version.
[contactsd] Do not use NEMO_CONTACT_MANAGER env var to select contact engine

Contact manager engine selection is now controlled globally rather than
per-process.
[contactsd] Only retrieve the self contact ID once

The self contact ID cannot change.
[contactsd] Remove duplication in debug output code
[contactsd] Remove un-batched update code

Batched updates are preferable.
[contactsd] Remove sparql telepathy variant

Only QtMobility Contacts interface is now supported by telepathy interface
plugin.
[contactds] Increment version number
Merge pull request #2 from matthewvogt/qtcontacts-update

Qtcontacts update