Limiting and scheduling large taxonomy ancestry changes

[thomaseverest]

@loarie

This means that if the ancestry is altered, for example if someone inserted taxon 8 between 1 and 2, then every observation associated with that branch needs to have its ancestry updated.

I’m guessing this is where indexing errors occur in bugs like this? Still a major issue of ants showing up in any search for Vespoidea, presumably due to this recent split. Would limiting these large changes limit these bugs, or is that dependent on number of descendant taxa and not observations?