obexd: Optimize tracker queries for PBAP
obexd: Optimize tracker queries for PBAP

Now data from tracker is fetched without redundand fields. Also
determining which type has phone, address and email (work or home) is
done in backend code - no tracker sub-query is used for that case. Now
queries are about 6 times faster for any amount of data( call history
queries, which were heavy loaded with OPTIONAL sub-queries are even 10
times faster than before)

ComputeCycles/bluez,ComputeCycles/bluez,ComputeCycles/bluez,mapfau/bluez,silent-snowman/bluez,silent-snowman/bluez,ComputeCycles/bluez,pkarasev3/bluez,mapfau/bluez,pstglia/external-bluetooth-bluez,pstglia/external-bluetooth-bluez,pstglia/external-bluetooth-bluez,pstglia/external-bluetooth-bluez,silent-snowman/bluez,silent-snowman/bluez,mapfau/bluez,mapfau/bluez,pkarasev3/bluez,pkarasev3/bluez,pkarasev3/bluez