feat: Add optional force option to updateRemoteFeatureFlags

[Cal-L]

Explanation

This PR just adds an optional force arg to updateRemoteFeatureFlags for forcing an update whenever it's set to true.
Example use case: We'll want to force an update once canonical IDs are available on the platform sides so that the proper flag variants are served

References

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Low Risk
Backward-compatible optional parameter with narrow cache-bypass behavior; existing callers unchanged when omitting force.

Overview
Adds an optional force argument (default false) to updateRemoteFeatureFlags, so callers can refresh remote flags from the API even when the cache is still valid—e.g. after a canonical profile ID becomes available so threshold segmentation can be re-fetched.

When force is true, the early return that skipped fetch on a fresh cache is bypassed; disabled controllers still never fetch, regardless of force. Messenger action types, JSDoc, changelog, and tests cover the enabled + forced path and the disabled + forced no-op.

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

[DDDDDanica]

LGTM !