feat: Enabled state filter (Frontend)

[kyle-ssg]

Thanks for submitting a PR! Please check the boxes below:

• I have run pre-commit to check linting
• I have added information to docs/ if required so people know about the feature!
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?
• I have used a Conventional Commit title for this Pull Request

Changes

Frontend functionality for filtering feature enabled state and feature value, based on #3541. This is controlled by the feature flag feature_enabled_state_filter.

Note: I believe the API is searching based on the project default_value/default_enabled, it should be based on the provided environment's feature state. We'd never want to filter based on defaults.

How did you test this code?

• Search a feature by value / enabled state

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2024 8:33am
flagsmith-frontend-preview	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2024 8:33am
flagsmith-frontend-staging	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2024 8:33am

[github-actions]

Uffizzi Preview deployment-47807 was deleted.

[zachaysan]

The code looks good thus far, but just wanted to confirm that we're designing in a search field as well to match feature values based on boolean, string, and integer values.

[kyle-ssg]

It’s an easy addition but I couldn’t imagine that common a use case , thinking about itI’ll do it as part of this pr

[zachaysan]

Code looks good, but please hold off on merging this until the server issue you highlighted gets fixed.

Edit: Or wrap this all up under a feature flag so we can deploy and fix whenever we want.

[kyle-ssg]

Yep its under a feature flag.