refactor(snap-network-utils): rename RemoteFeatureFlagProvider to RemoteFeatureFlagsProvider

[ulissesferreira]

Explanation

RemoteFeatureFlagProvider was introduced in #99 and exported in #102 as a shared utility for reading remote feature flags from Core via RemoteFeatureFlagController:getState. The singular Flag naming was inconsistent with the controller (RemoteFeatureFlagController) and our other pluralized provider exports (e.g. AssetsProvider), and it reads awkwardly for a class that returns multiple flags via getFeatureFlags.

This PR renames the provider and its related symbols to use Flags (plural):

Before	After
RemoteFeatureFlagProvider	RemoteFeatureFlagsProvider
RemoteFeatureFlagProviderMessenger	RemoteFeatureFlagsProviderMessenger
REMOTE_FEATURE_FLAG_PROVIDER_NAME	REMOTE_FEATURE_FLAGS_PROVIDER_NAME

Source files are renamed accordingly (RemoteFeatureFlagsProvider.ts, RemoteFeatureFlagsProvider.test.ts). Package exports in src/index.ts are updated to match.

Note: The Core controller action and types remain RemoteFeatureFlagController / RemoteFeatureFlagController:getState (singular Flag) — only the snap-networks-utils provider namespace and exports change.

No consumers in this repo or downstream snaps currently import the old singular names, so this is a low-risk rename ahead of broader adoption.

References

• Related to WPN-1790
• Follows feat(snap-networks-utils): add shared RemoteFeatureFlagProvider #99 (introduced RemoteFeatureFlagProvider)
• Follows fix(snap-networks-utils): export RemoteFeatureFlagProvider #102 (exported provider from package entrypoint)

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

[taran-a]

LGTM