Python: fix(core): keep booleans distinct from numbers inside sets

[Anish Mehta (anishmehta24)]

Motivation & Context

filter_values_equal keeps booleans distinct from numbers for scalars, sequences and mappings, but not for sets — and require_filter_collection accepts sets and frozensets as filter values:

filter_values_equal([True], [1])   # False, correct
filter_values_equal({True}, {1})   # True,  the bug

A set cannot be walked pairwise the way the sequence branch walks a list, so it fell through to plain ==, and {1} == {True} is true in Python because True hashes and compares equal to 1.

It reaches real filtering: _evaluate_filter uses this for eq, ne, in, not_in, contains, contains_any and contains_all, so a record whose field is {1} matched a filter looking for {True}.

Description & Review Guide

• What are the major changes? A set branch in filter_values_equal that compares members by _set_member_key, which tags bools and recurses through the hashable containers a set can hold (tuples, frozensets). When only one side is a set, native == still decides, so a set never equals a list or a mapping.
• What is the impact of these changes? {True} no longer equals {1}. Everything else is unchanged: {1} still equals {1.0} (ints and floats stay interchangeable, matching the existing scalar case), and {1} still equals frozenset({1}), which Python compares equal by contents.
• What do you want reviewers to focus on? Whether set-versus-frozenset should stay equal. I kept Python's own answer for consistency with the "preserve native container semantics" comment on the sequence branch, and added both cases to the table so the choice is pinned either way.

Tests: ten cases added to the existing test_filter_values_equal_preserves_nested_types table, which had no set or frozenset case at all — the bool/int pairs for set, frozenset and a nested tuple, plus the unchanged behaviour ({1}/{1.0}, ordering, length mismatch, empty, set vs frozenset, set vs list). Five fail on main.

test_vectors.py 194 passed. poe fmt, poe lint, poe typing -P core clean.

Related Issue

Fixes #8679

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR is linked to an issue and there is no other open PR for this issue (see Related Issue above).
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Eduard van Valkenburg (eavanvalkenburg)]

Anish Mehta (@anishmehta24) The current head is green, and the dedicated full-diff review found no remaining actionable issues with the strict boolean/number set comparison change.