fix: update-env-state-on-metadata-update

[Zaimwa9]

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

• I have read the Contributing Guide.
• 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.

Changes

Updating custom fields did not update the local env state that is used in the general page. It forced user to refresh after having updated the fields to be able to correctly save the general data.

• Update local env state after custom fields successful update

How did you test this code?

• In dashboard

Steps to reproduce:

1. Create a custom fields required on environment
2. Toggle change requests (will fail)
3. Go to Custom fields and update the value
4. Go back to toggle change requests (would still fail until refresh)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
flagsmith-frontend-preview	Ready	Preview, Comment	Mar 3, 2026 8:23am
flagsmith-frontend-staging	Ready	Preview, Comment	Mar 3, 2026 8:23am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Ignored		Mar 3, 2026 8:23am

[github-actions]

Docker builds report

Image	Build Status	Security report
ghcr.io/flagsmith/flagsmith-api-test:pr-6831	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-e2e:pr-6831	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-api:pr-6831	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith:pr-6831	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-private-cloud:pr-6831	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-frontend:pr-6831	Finished ✅	Results ✅