WB does not always match COT to determination

[emenslin]

Describe the bug
Uploading a CO data set to workbench with multiple trees can sometimes led to CO with a COT and determination that do not match. No error is thrown and there is seemingly nothing wrong with the uploaded records (no unload protect, save blocker, etc.) but the determination is part of another tree. I didn't get a chance to do a whole ton of testing so there might be other weird behavior with uploading CO/COT/determinations in workbench that I didn't notice.

To Reproduce
Steps to reproduce the behavior:

1. Go to workbench
2. Select CO as base table
3. Add mappings for cat #, COT, and to at least one rank from two different trees (example upload plan: COT test.json)
4. Add an existing taxon from a tree that is not the same as the COT
5. Validate
6. See no errors are thrown
7. Upload
8. See record looks normal
9. Query/go to tree and see taxon is from a different tree

Expected behavior
Some sort of error should be thrown in the cell in workbench so you cannot upload without fixing it. There might be a better solution because I know errors aren't always ideal but this should definitely be caught before upload.

Screenshots

Tree for each COT:

Taxon trees:

01-31_16.11.mp4

Actual upload:

01-31_16.12.mp4

Please fill out the following information manually:

• OS: Windows 11
• Browser: Chrome
• Specify 7 Version: production
• Database Name: ojsmnh
• Collection name: fossil invertebrates
• User Name: spadmin
• URL: https://ojsmnh110242024production-production.test.specifysystems.org/specify/workbench/101/

Additional context
I was not able to check everything but some other COT behavior in workbench is that; if there is no COT, all taxa are uploaded to the default tree (expected behavior as far as I know), if there’s only one tree but multiple COTs, it will upload taxon to whatever tree is mapped no matter what the type is, this is also a problem but if it needs to be a separate issue let me know.

01-31_16.56.mp4