fix: Log the isFlagKnown cached-data warning only once per client

[kinyoklion]

Summary

While the client is not initialized but the data store already holds data, isFlagKnown logs a warning on every call. A client that stays in that state, for example one serving persisted data before its data source connects, emits that warning for every check, which floods the log without adding information.

The warning now logs once per LDClient instance. The check-and-set uses an AtomicBoolean.compareAndSet, which is lock-free and only runs on the path where the warning may be needed, so normal calls are unaffected. The message says that it is logged once.

The sibling message for an uninitialized store, and the gating condition itself, are unchanged. The evaluation path in this SDK has no equivalent cached-data message, so isFlagKnown is the only site.

---

Note

Overview
Stops log spam when isFlagKnown runs before the client finishes initializing but the data store already has cached flag data.

LDClient now keeps an AtomicBoolean and uses compareAndSet so the “using last known values from data store” warning is emitted once per client instance; the text notes that it is logged once. Behavior for uninitialized stores (still warn every call and return false) and for flag lookup itself is unchanged.

Adds isFlagKnownLogsCachedDataWarningOnlyOnce to assert two isFlagKnown calls in that state produce a single WARN.

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