merge function does not account for node revision id (vid) and term id (tid) as primary key of term_node table

The key on term_node table is (tid,vid). When merging records, one often gets primary key errors because taxonomy_manager_merge is inserting a 0 for the revision ID in the term_node table. When merging multiple nodes into one term, this inevitably violates primary key constraints.