Determination taxon query combo box should be filtering by COT tree

[grantfitzsimmons]

Originally a component of #4640

• When the user creates a new determination, the taxon tree searched when entering a taxon or preferredTaxon value must be based on the object type's tree (if objectType is present), otherwise it should use the discipline default

I've discussed this with Caroline and it will be done sometime before the MVP if possible. I have found this to be a really important user interface issue.

Issue: The Taxon QCBX on the Determination form does not filter based on the selected Collection Object Type (COT)'s associated taxon tree.

Solution: Filter the QCBX based on the associated Collection Object’s (CO) COT’s tree.

Rationale: When searching for a taxon name, the results currently show names from all taxon trees. This is cumbersome as it

1. Slows the application for the user as it loads dozens of names that are not relevant or desired based on the type
2. Enables users to select a name that prevents the record from being saved.
3. The Collection Object Type can be an obstacle when its sole purpose is to validate the tree node

This should not be defined in any special way via the XML– it should only use the database relationships. If no type is selected, it should follow the default type for the collection.