Batch Edit: Batch edit for (multiple) trees

[sharadsw]

Component of #4929

• Trees

  There are two different routes to perform tree updates.

  • Workbench method:
    
    If you want to modify a specific rank, or say reassign species for determination, you'd want to add a specific rank in the query. In this case, it always matches and uploads (and possibly clone), so we don't have updates.
    In the query builder, it'll enforce that you select complete branch of the tree. That is, if your query contains rank "species", and "genus", it'll demand you to add ranks all the way down from "genus" to "species". If used part of a relationship, it'll demand going the way down from "genus" to the lowest rank in the tree.

  • Update method:
    
    If in the query builder, there is no visible tree rank field, it allows direct modifications (and, thus, updates) to the tree table. This will be useful if you want to, say, update remarks for ones that match name "ploia"

Notes from #5417:

• Batch edit currently doesn't work for multiple trees. Relevant code to consider: Batch Edit: Support for editing basic fields #5417 (comment)
• Adding tree ranks to a query for batch edit does not work as expected. See: Batch Edit: Support for editing basic fields #5417 (review)

[sharadsw]

Ensure missing ranks error work as expected:

In #5417 (see: #5417 (review)) :
Missing ranks are calculated by checking rank ids across all trees, leading to duplicates.

Expected behavior:

If you selected species (and if species is the last rank), it will not ask for more ranks. If you selected genus, and there are subspecies and species rank below it, then it would force you to select species and subspecies. Basically, all the ranks below the highest rank need to be selected. It gets complicated in cases of relationships (determinations -> taxon) otherwise.

[sharadsw]

Improvements:

• Check if is_tree_table is still needed (Batch Edit: Support for editing basic fields #5417 (comment))