feat: Add explicit ordering for segment rule conditions

[khvn26]

Thanks for submitting a PR! Please check the boxes below:

• I have added information to docs/ if required so people know about the feature!
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?
• I have used a Conventional Commit title for this Pull Request

Changes

This adds a SEGMENT_RULES_CONDITIONS_EXPLICIT_ORDERING_ENABLED setting to force ORDER BY id ASC clause to all segment condition selects, which remedies the existing problem with no guaranteed ordering (#5669).

How did you test this code?

Modified the existing view test to use the setting and avoid the explicit test data result ordering, which obviously masked the problem in the first place.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs	⬜️ Ignored (Inspect)	Visit Preview		Jul 1, 2025 9:31am
flagsmith-frontend-preview	⬜️ Ignored (Inspect)	Visit Preview		Jul 1, 2025 9:31am
flagsmith-frontend-staging	⬜️ Ignored (Inspect)	Visit Preview		Jul 1, 2025 9:31am

[github-actions]

Docker builds report

Image	Build Status	Security report
ghcr.io/flagsmith/flagsmith-api-test:pr-5671	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-e2e:pr-5671	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-frontend:pr-5671	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-api:pr-5671	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith:pr-5671	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-private-cloud:pr-5671	Finished ✅	Results ✅

[emyller]

LGTM without a comment typo.

I think you mentioned the possibility of making SEGMENT_RULES_CONDITIONS_EXPLICIT_ORDERING_ENABLED = True default for new users. Is that something we'd like to pursue in this PR?

[khvn26]

the possibility of making SEGMENT_RULES_CONDITIONS_EXPLICIT_ORDERING_ENABLED = True default for new users. Is that something we'd like to pursue in this PR?

Not in this PR, as it's intended to quickly unblock a customer.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.76%. Comparing base (0235f18) to head (1be4c5a).
Report is 5 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5671   +/-   ##
=======================================
  Coverage   97.76%   97.76%           
=======================================
  Files        1245     1245           
  Lines       44062    44071    +9     
=======================================
+ Hits        43076    43085    +9     
  Misses        986      986           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.