Rule engine as a separate NuGet package

Requesting a standalone Flagsmith Engine NuGet package, separate from the Flagsmith Client NuGet, for flexible rule evaluation without the full SDK.

Why:

I need a lightweight rule engine for custom use cases, bypassing the client’s networking and polling features.

Benefits:

Lean Engine: Minimal package for evaluating rules with my own data, reducing overhead.
Custom Polling: Freedom to implement my own polling strategy or data source.
Event Notification: Tailored event handling to fit my app’s architecture.
Less Dependencies: Avoids unnecessary dependencies like Polly, simplifying integration and minimizing version conflicts.
Metadata Enrichments: Single location to extend features with additional metadata such as tags.

Proposal:

A dependency-free package with rule evaluation logic, no networking, and optional event hooks, which should be considerably easy to implement by extracting the existing rule evaluation logic into a standalone library.

Conclusion:

This would enhance flexibility and support advanced scenarios where the full client isn’t needed. Thoughts?

Start by locating the existing rule evaluation logic in the Flagsmith Client NuGet package and reviewing how it depends on networking, polling, Polly, and event handling. Define the boundaries for a standalone, dependency-free Engine package before changing code. Done means the engine can evaluate rules with caller-supplied data and is publishable separately from the full client.

Written by the indexing model from the issue text.