tests: Modify TrackerBatch asynchronous execution test

This function was pushing things a bit too hard our guarantees,
while that works on direct connections, remote connections may
have order inverted by the asynchronicities involved in writing
updates through pipes, so we may end up "heisenbugs" like:

Tracker:ERROR:../tests/libtracker-sparql/tracker-batch-test.c:189:assert_photo: assertion failed (tracker_sparql_cursor_get_integer (cursor, 1) == horizontal_res): (234 == 123)

The one guarantee we can do is: After execute_finish() returns,
the batch was inserted. So adapt the existing test and add a new
one to probe that.

0 files changed, 0 insertions, 0 deletions