Compiler set intersections always iterate the first input

React version

Current main (2dc7da790d63).

Steps to reproduce

1. Call the compiler utility Set_intersect with a large first set, another large set, and a very small later set.
2. Count membership checks in each remaining input.

Current behavior

The utility checks remaining sets in their supplied order for every element of the first set. Its live compiler use intersects predecessor assumedNonNullObjects; when an early large predecessor is followed by a tiny one, most impossible candidates still incur checks against the larger set before the small set rejects them.

Expected behavior

Keep iterating the first set so result insertion order is stable, but probe the smallest remaining set first. Non-members then short-circuit before larger-set checks without changing intersection values or order.

Start by locating the compiler utility Set_intersect and its live use with assumedNonNullObjects. Exercise the case with a large first set and a tiny later set, then verify that the smallest remaining set is probed first while intersection values and insertion order stay unchanged.