feat: versioned segment override change request

[kyle-ssg]

trafficstars

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

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

Changes

• Environments with versioning + Change Requests enabled will now have the ability to create a change request for segment overrides

• Change requests now diff all of the feature states in comparison to live, irrespective of if versioning is enabled.

Much like versioning this will tell you changed, created and unchanged values

• The create feature modal toast will now differentiate when a change request was created vs editing a feature. Creating a change request will close the create feature modal

• Removed a confusing unused field "hide_from_client" from feature states

• Note: versioned change requests cannot be edited due to the limited use case and complexity of updating a versions feature states in a change request.

How did you test this code?

• Created, edited and removed segment overrides in a change request on an environment with versioning

[vercel[bot]]

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	May 8, 2024 1:07pm
flagsmith-frontend-preview	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 8, 2024 1:07pm
flagsmith-frontend-staging	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 8, 2024 1:07pm

[github-actions[bot]]

Uffizzi Preview deployment-50354 was deleted.

[matthewelwell]

@kyle-ssg I've just noticed that the change request view doesn't actually show which segment a feature is being overridden by?

[matthewelwell]

Also, is there anything we can do to improve the view when you remove a segment override? I'm just seeing this

[kyle-ssg]

@matthewelwell both issues should be resolved now

[matthewelwell]

@kyle-ssg when you create a CR with more than one segment override, the priority values don't seem right.

[matthewelwell]

@kyle-ssg I can't create any change requests now with segment overrides following the latest change:

[kyle-ssg]

Related #1204

[rolodato]

@kyle-ssg Did we decide to explicitly exclude scheduling changes on segment overrides on environments without change requests enabled?

Editing a feature's state without change requests enabled let you schedule changes:

In comparison, editing segment overrides without change requests only let you make an immediate update: