Context through persistent queue

[mackjmr]

Is your feature request related to a problem? Please describe.
Currently, context gets lost when persistant queue is used. The context gets lost in the call to Batch. Batch is an interface, and is implemented by the storage system. For filestorage, the call to Batch does not use the context at all.

This poses issues for #8804. One of the proposed solutions is to instrument the consumer. Because of the above, the context will be lost between the consumer span and the export span. See the following comment: #8804 (comment) for a more detailed view of the issue

Describe the solution you'd like
Keep track of context (or at least trace ID) across persistant queue. If internal instrumentation is the only use case, we could add the trace_id to the info we put in the queue. At the time the queue is read, we can use the trace ID to link both spans (span link, or parent/child).