Filter Collection Objects by COT formatter in Queries

[sharadsw]

If you select a COT formatter when querying catalog numbers, the results also include COs that do not follow the selected formatter leading to inconsistent and strange looking results.

From @combs-a:

Here is an example query and its result (on this PR):

And another, where we've changed the query to search for any record greater than the lowest result in the previous...

Now 2024-000001 is greater than 230, when 230 was greater than it before, which is definitely a bit of strange behavior.

If it would be possible, it may be a good idea to still have some kind of filter to automatically only include results that are of the COT selected, perhaps. This is possible by just selecting the name of the COT, but that does not support cases in which you want to query for COs with different COTs.

I think for an example query and expected result, it'd be something like:

Catalog Number -> Greater Than -> 2025-000001 [COT: FossilTest]
OR -> Equal -> 1 [COT: Vertebrate Paleontology]

Results:
Any CO that has the COT FossilTest with a catalog number greater than 2025-000001 as well as the CO that has the COT Vertebrate Paleontology

From @emenslin:

Results are not being filtered properly. Not sure the exact logic here but for some cat # they show up in the results when they shouldn't or they don't show up in results when they should. In this video I query on cat # greater than 2025-001 and you can see that '2025-001' shows up when it should not and then when I query on equal to 2025-001 it doesn't show up when it should. This does not seem to be consistent with every cat # in a db but I was able to recreate on ojsmnh and chadron.

02-17_14.12.mp4