[libcontacts] Prioritize requests that make app startup more responsive

startRequest was changed to give priority to ensureComplete and
addressResolve calls.
do favorites model first
[performance] Schedule resolveAddress immediately

resolveAddress requests are done with one query at a time, in
order to correlate the results with the looked-up addresses.
Doing them sequentially via UpdateRequest events added a lot
of overhead in the form of coordination between threads.

This commit creates a dedicated QContactFetchRequest for each
resolveAddress call, so that the events for starting them can
arrive all together in the backend thread and the events
announcing the results can arrive all together in the UI thread.
They will still be processed sequentially, but this change cuts
out the delay between finishing one request and starting the next.

In tests with 10k contacts and a recent contacts list with limit=20,
this reduced the resolve time from 1s to 0.3s.
[performance] look up address resolve requests in a QHash

This change does not affect normal performance but it guards
against bad performance when there are many resolve requests.

Thanks to Matthew Vogt for the idea.
[tests] Test address resolution in SeasideCache
[tests] in resolveDuringContactLink check if link went ok

change suggested in review by mvogt
Merge pull request #95 from amtep/master

[libcontacts] Prioritize requests that make app startup more responsive