Manage context per named provider when using the static-context paradigm

[beeme1mr]

Overview

When an SDK follows the static-context paradigm, context can only be managed from global API object. This is to convey to application authors that changing context may lead to an expensive async operation.

Currently, there's a global evaluation context that's shared across all providers. This can lead to challenges like:

• Updating context fires the onContextChange handler for all registered providers.
• Unable to manage context for a specific provider.
• Context that's valid for one provider may be invalid in another.

Requirements

• Define the requirements for managing context per named provider when using the static-context paradigm

References

• Allow evaluation context to be managed per provider in the web SDK js-sdk#685

[toddbaert]

I like the suggestion here.