Description
As discussed in #8542 (comment) the annotation merging code changes the ids of the elements to avoid duplicates, but does so in an inconsistent fashion. Usually, the ids of the elements from tracing A are remapped, but in case of segmentIds it’s those from B. (It’s also sometimes both, when there are id densifying or deduplication steps as for nodes and boundingboxes respectively).
@MichaelBuessemeyer noted that it would read more intuitively if the one with the remapped ids would also be called tracingB.
I believe we can change this logic without breaking relevant parts of backwards compatibility.
Note that the segment id remapping is dictated by the code that acutally merges the volume data. Not sure how (or if) it works for editable mappings.