Feat(UI): add ability to collapse/expand strategies

[wuguishifu]

About the changes

• Added a button to collapse/expand the targeting section of the strategies.
• When collapsed, the rollout percentage and variants are shown.

Expanded (default):

Collapsed:

Closes #9529

Important files

• The main functionality is located in the directory /frontend/src/component/feature/FeatureView/FeatureOverview/FeatureOverviewEnvironments/FeatureOverviewEnvironment/EnvironmentAccordionBody/StrategyDraggableItem/StrategyItem/CollapseStrategyIcon

Discussion points

• Right now it seems like for environments the expanded/collapsed state isn't cached at all so refreshing the page resets the state. I followed this behavior for this PR as well, but maybe instead the state should be stored in cookies so it persists across sessions.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
unleash-monorepo-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 16, 2025 6:03am

[vercel]

@wuguishifu is attempting to deploy a commit to the unleash-team Team on Vercel.

A member of the Team first needs to authorize it.

[thomasheartman]

Hi, @wuguishifu 👋🏼 Thanks for the contribution 😄 As was mentioned in the issue you linked, we've registered this as a feature request and are talking about it internally at the moment.

As you might have noticed, we're working on a pretty big strategy UI update right now, and this falls squarely in the middle of it (and also aligns with our stated goals of the updated interface). Because we're right in the middle of it, we'd like to take this chance to have our UX team think about this fully (what to show / hide, consequences of showing/hiding, tradeoffs, etc) before we implement it. That also means that we're not going to merge this right now.

But to help us understand what the need for this is, it would be interesting to hear your take on why you want this functionality. Could you tell me what problems this solves for you?

Anyway, because we are right in the middle of an update of the strategy rendering code, any files you touch there are likely to cause conflicts, so to keep us all from going bananas with merge conflicts, I'd recommend waiting a little bit before updating this PR anyway 😅