Query operator `OR` breaks with two true/non-negated fields

[bronwyncombs]

Describe the bug
A clear and concise description of what the bug is.

Queries run with the OR operator, such that more than one value is true (not negated), don't return results in v7.10.2.2

To Reproduce
Steps to reproduce the behavior:

1. Go to DB running v7.10.2.2
2. Run query with OR operator and more than true field (not-negated field)
3. See no results
4. Compare to same query in v7.9, see results

Expected behavior
Return results as queries upon and received in previous versions

Screenshots

v7.9

v7.10

v7.10 | results when only one OR value is true

Please fill out the following information manually:

• OS: macOS
• Browser: Chrome
• Specify 7 Version: v7.10.2.2 (not present in 7.10.1)
• Database Name: uw-geocollections
• Collection name: vertebrate fossils
• User Name: spadmin
• URL: test panel

Reported By
Nate Shoobs @ OSU Mollusks

Additional context

Nate reported this issue to the forum (see post). The post there includes additional screenshots, JSON for query used, and links to both instances they have running on two separate versions. The OSU one runs a commit from 3 months ago (SHA: e1e47642f98ffc3e7e54c6cba50f79c3d38f9b2e) and the other in on NA server

I recreated this on the test panel using Nate's query, adjusting taxon values for the UW-GeoCollections taxon data.

[specifysoftware]

This issue has been mentioned on Specify Community Forum. There might be relevant details there:

https://discourse.specifysoftware.org/t/or-queries-on-tree-fields-with-certain-combinations-of-operators-are-broken-by-7-10-2-2/2544/2

[grantfitzsimmons]

@bronwyncombs Did you test this in v7.10.2?

[sharadsw]

Seems to be fixed in production: https://uwgeocollections20250210-production.test.specifysystems.org/specify/query/153/

[CarolineDenis]

@sharadsw @bronwyncombs
If fixed we can close this

[grantfitzsimmons]

@sharadsw @CarolineDenis We can't wait until 7.11 to fix this issue– it is a regression introduced by #6473 specific to v7.11.2.2.

[realVinayak]

Ugh sorry about this. FYI, this was introduced by me in original 4929 PR. See this thread: #6196 (comment). Later, it was fixed by Sharad (see aa81431). Backport that commit?