feat: Add sane defaults for segment_operators, integration_data, saml flags

[rolodato]

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

• 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?
• I have used a Conventional Commit title for this Pull Request

Changes

Add default values to the FoF flags segment_operators, integration_data, and saml. This avoids the following scenario:

1. Customer is setting up self-hosted environment, everything works fine
2. FoF environment is created with only a few specific flags that the customer wants to modify
3. Creating segments and trying to use the "Single Sign-On" button at the login page no longer works, unless the segment_operators and saml flags are created with the correct values.

The flags all still work as usual, but don't break anything if they don't exist in a FoF environment.

integration_data is a bonus to have integrations work out of the box.

How did you test this code?

In a local environment, set up FoF but do not create any flags. These should still work:

• Creating segments
• Viewing and creating integrations
• Clicking the "Single Sign-On" button in the home page

[vercel]

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	Aug 28, 2024 9:21pm
flagsmith-frontend-preview	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 28, 2024 9:21pm
flagsmith-frontend-staging	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 28, 2024 9:21pm

[github-actions]

Docker builds report

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

[github-actions]

Uffizzi Preview deployment-55668 was deleted.

[matthewelwell]

I've added one specific comment, but I'm also interested to know if / how we plan to keep the defaults in sync with any changes to the flags in production.

I'm also keen to know @kyle-ssg 's opinion on this of course.

[rolodato]

I'm also interested to know if / how we plan to keep the defaults in sync with any changes to the flags in production.

• segment_operators: I see 2 options here:
  1. Keep making manual changes to the hardcoded defaults at the same time we make changes to production. Changes to segment operators are rare enough that this is probably fine
  2. Deprecate this flag and plan to remove it. This seems awkward to do given the dependency on production SaaS - one way I could see this happening is by passing in a transient version trait while fetching FoF flags, and creating a segment override on segment_operators that removes its value if this trait version is set. This keeps old instances working, lets users customise segment_operators on their own FoF, and frees us from needing to make changes to this flag again.
• integration_data: Same options as for segment_operators
• saml: This flag will probably never be changed in production