test: add missing negation operator tests for TEXT, NUMBER, and compound rules

[hariombalhara]

What does this PR do?

Adds additional integration test coverage for the exclusion/negation attribute filter regression fixed in #27669. During review of that PR, the following test gaps were identified:

1. TEXT type negation operators — not_equal and not_like with users who have no TEXT attribute assigned
2. NUMBER type negation operators — not_equal with users who have no NUMBER attribute assigned
3. Compound rules with partial attribute presence — a positive rule AND a negation rule where a user has one attribute but is missing the other (negated) one
4. Multiple negation rules — two select_not_equals rules where users are missing different attributes

These 5 new tests complement the 8 tests added in #27669 (which covered SINGLE_SELECT and MULTI_SELECT negation operators).

No production code changes — test-only.

Updates since last revision

• Resolved merge conflicts with main (the test file was renamed from .test.ts to .integration-test.ts on main)
• Converted all 5 new tests from unit-test style (mocked scenarios, hardcoded userIds) to integration-test style (real DB via createAttributesScenario, dynamic createdUsers[n].userId, testFixtures.team.id/testFixtures.org.id)
• Reverted non-intentional changes to AddMembersWithSwitch.tsx — the diff now contains only test additions

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A — test-only change.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

Run the integration test file:

TZ=UTC VITEST_MODE=integration yarn test packages/features/routing-forms/lib/findTeamMembersMatchingAttributeLogic.integration-test.ts

All tests should pass, including the 5 new ones for TEXT/NUMBER negation and compound rules.

Things for reviewer to verify

• TEXT and NUMBER attributes define explicit options in the test to work with createAttributesScenario's option-to-user mapping. Verify this accurately represents how these attribute types store values in production.
• The TEXT tests use buildQueryValue directly (instead of buildSelectTypeFieldQueryValue) because TEXT/NUMBER fields need valueType: ["text"]/["number"] rather than the default ["select"].
• NUMBER attribute values are stored as strings ("5", "10") in the scenario, which matches how the system processes them through caseInsensitive(getValueOfAttributeOption(...)). Confirm this is accurate.
• The compound-rule tests assume RAQB defaults to AND conjunction when properties.conjunction is not explicitly set in the query value. Confirm this matches production behavior.

---

Link to Devin run: https://app.devin.ai/sessions/cf62bcf87df84468b26928d8681738ee
Requested by: @hariombalhara

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 4 additional findings.

[cubic-dev-ai]

No issues found across 1 file

[github-actions]

E2E results are ready!

• Workflow #104908.1 latest results