Updating a variation in a multivariate flag when change requests are enabled immediately changes the variation

[matthewelwell]

How are you running Flagsmith

• Self Hosted with Docker
• Self Hosted with Kubernetes
• SaaS at flagsmith.com
• Some other way (add details in description below)

Describe the bug

Update a variation in a multivariate flag when change requests are enabled immediately changes the variation

Steps To Reproduce

Setup:

1. Project with at least 1 multivariate flag
2. Environment with Feature change requests enabled

Steps:

1. Modify one of the variations of a multivariate flag
2. Click 'Create Change Request' and submit the resulting form to create the change request (notice that no user feedback is given regarding the variation update)
3. Refresh the feature and notice that the variation has been updated directly, rather than being added to the change request

Expected behavior

Ideally, the variation update would be included in the change request.

Some alternatives that would at least be better than the current UX:

1. the user is provided with feedback that the variation will be updated immediately on submitting the change request (still pretty bad UX tbh)
2. the variations are updated through a separate process outside of the change request creation flow that provides the user with sufficient feedback

The second alternative option here is likely the best immediate change that we can make without moving certain parts of 'feature change requests' to the project level, which is already the longer term goal.

Screenshots

No response