docs: fix a bug in the search results in which clicking a sorting tab

does not open that tab until you click a tab again. This occured due
to the order of events being out of order in terms of when we invoke
the click() on a tab based on the search being invoked. I'm pretty sure
this worked fine before, so I think this might have been introduced
by a behavior change in CSE. The fix is to simply invoke the click()
for a tab when the respective search results actually return using
an additional callback.

Change-Id: Ib58fdc75b3095ca2a3a2f5f892e778acdbc1dacd