The outer trace of a n1ql query needs a couple more tags.

When we have a scoped query (query or analytics), we should add the bucket and scope to the outer trace as tags. But the bindings pass in a json string of the entire request, rather than an object we can easily crack open.

We can do one of 2 things: Pass a dict instead of a string, making that simple enough. Or, pass the query_context in as a dict separately. I did the latter for search, as it was only one field and simple enough. Right now, the db.statement contains the statement, the params, the query_context, etc... So it is there, but not easily searchable.

Ideally the db.statement would only be the statement itself. This is a good reason to pass in a dict, but we'd have to then make several lcb_cmdquery_xxx calls depending on what is in the dict. So – perhaps we pass the statement, and the query_context in addition to the stringified request.