Clarify default query constraint compound behavior

[mcandre]

By default, sending multiple constraints to upper.io Find() behaves as a union (OR), which may surprise users expecting an intersection (AND). Can we make this default behavior more clear in the documentation and examples?

[Asday]

I would argue against changing such a fundamental default, given that the library is presumably used in several thousand codebases.