feat: Add the override marker to the flag and segment models and mark evaluations

[kinyoklion]

Summary

Adds the override marker to the flag and segment models and makes the evaluator mark evaluations as override-affected, as defined by the OVERRIDE specification.

FeatureFlag and Segment gain an internal IsOverride property and an AsOverride() method that returns a marked copy sharing the immutable parts of the original. The marker lives on the model only: the JSON converters do not write it, so a marked definition serializes exactly like an unmarked one, and the original object handed to AsOverride() is never modified.

The evaluator marks an evaluation when any definition it read carried the marker: the evaluated flag, a prerequisite flag at any depth, or a segment consulted during clause matching, whether or not the segment matched. The marking propagates upward only. Each prerequisite evaluation is a scope of its own that starts from the prerequisite's marker, so the record for a prerequisite reflects only its own subtree, while the parent scope absorbs the nested marking when the nested evaluation returns or throws. Error results are marked too: a malformed override flag, a prerequisite cycle through an override flag, and an invalid context all produce an error reason that carries the indicator. A definition that cannot be resolved contributes nothing. The marking is reported through the reason's OverrideAffected indicator from the previous change in this series.

Nothing in this change produces marked definitions yet; the override store that does so is the next change. Every existing evaluation therefore behaves as before, which the existing evaluator tests confirm. The new tests cover each marking case, including the prerequisite tree in the specification where only one leaf is overridden.

This PR is based on the branch of the EvaluationReason indicator change, which it depends on.

SDK-3248

---

Note

Overview
Adds an internal override marker on FeatureFlag and Segment (IsOverride / AsOverride()), kept only in memory and not in serialized JSON.

The evaluator tracks whether an evaluation was override-affected when any definition actually read during that evaluation was marked: the root flag, nested prerequisite flags (each prereq gets its own scope; marking bubbles up to the parent), or segments loaded for clause matching (including non-matches and negated clauses). That flag is attached to the top-level EvaluationReason (and prerequisite eval records) via WithOverrideAffected, including error paths. Unresolved flags/segments do not contribute.

Extensive tests cover marking rules, serialization of markers, and interaction with big-segments status. Nothing in this PR yet supplies override definitions from an override store—that is follow-up work; default behavior for unmarked definitions is unchanged.

^{Reviewed by Cursor Bugbot for commit 511de7f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[kinyoklion]

bugbot review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 511de7f. Configure here.}