UI/UX: Standardize the save workflow for Feature Toggles, Values, and Segment Overrides

Currently, there is a significant inconsistency in how changes are saved across the UI, causing confusion and friction for our development team.

Scenario A (List View): Toggling a feature to enable/disable happens immediately with no secondary approval or confirmation.

Scenario B (Detail View): Changing a feature's value requires clicking "Update Feature Value".

Scenario C (Segment Overrides): Editing a segment override requires a nested two-step process: you must "Apply" the change for the segment override, and then remember to click "Update Feature Value" at the top/bottom of the page.

Our developers frequently change a segment override and forget the second global "Update" step, assuming the "Apply" button saved their work. The mix of immediate saves (toggles) and nested manual saves (overrides) is very confusing.

### Describe the solution you'd like.

If a full "Sticky Action Bar" overhaul is too heavy, a lighter alternative would be Visual Highlighting & Auto-scroll:

When a user clicks "Apply" on a segment override, the UI should immediately scroll or jump to the main "Update Feature Value" button.

The "Update Feature Value" button should pulse, change to a high-contrast color, or display a badge (e.g., "1 Unsaved Change") so the developer clearly knows the transaction is not yet complete.

### Describe alternatives you've considered

Maybe also prevent closing the details panel if changes not applied, let the user option to ignore and discard.

### Additional context

Feature flags directly impact production environments. A unified, highly visible "Publish" workflow reduces the risk of accidental deployments and eliminates the frustration of "lost" work when devs navigate away before completing the nested save steps.