Validate Feature Flag Associations

What does this MR do?

Validate associations for feature flags based on version.

• Version 1 (legacy) feature flags may be associated only with Operations::FeatureFlagScope models.
• Version 2 (new) feature flags may be associated only with Operations::FeatureFlags::Strategy models.

This also tweaks the conditions under which we create the default scope so that we create it only for version 1 flags.

Issue: #204895 (closed)

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team