This does two main things. First, it tracks sets of obsolete document
IDs and retries obsoletes and deletes. Second, it tracks document IDs
that are attempted to be written to the server for obsolescence or
deletion without waiting for a server response to prevent orphaning
documents on successful upload and failed response.
The ObsoleteDocumentTracker uses a JSON map to maintain obsolete
document IDs and priority values. That's not the right data
structure; Bug 894194 tracks improving it.