[FEATURE] client evaluation context support

[aepfli]

Within other SDKs, we're able to set a context on a client level. Although there is a field within the client, there is no setter for the evaluation context.

We should be able to set a client wide evaluation context, and it should behave as described.

see https://github.com/open-feature/spec/blob/main/specification/assets/gherkin/contextMerging.feature

[vikasrao23]

Hi! 👋

I've implemented this feature in PR #565.

What was added

• set_evaluation_context(context) method to the OpenFeatureClient class
• Comprehensive tests verifying the setter works and context merging is correct

Implementation details

The client context is now settable and is properly merged during flag evaluation with the correct precedence:

API context → Transaction context → Client context → Invocation context

This matches the behavior described in the OpenFeature spec's context merging feature.

Example usage:

client = api.get_client()
client.set_evaluation_context(EvaluationContext(
    targeting_key="user-123",
    attributes={"email": "user@example.com"}
))

Let me know if any adjustments are needed!

[balgaly]

I'd like to tackle this — plan to add set_evaluation_context() on the client and merge it with the provider-level context per the spec. PR coming shortly.

[danjuv]

Perhaps this issue needs rescoping. @gruebel mentioned the solution is the missing E2E tests but that's not immediately clear from the description.