[App Configuration] Removed enabled/conditions from feature flag required properties

[linglingye001]

Making enabled and conditions optional according to the Feature Flag schema, where only id is required.

[Copilot]

Pull request overview

This PR makes the enabled and conditions properties optional for feature flags, aligning with the Feature Flag v2.0.0 schema where only id is required. This enhances flexibility by allowing minimal feature flag definitions.

Key Changes:

• Removed enabled and conditions from the required properties validation array
• Added comprehensive test coverage for feature flags with optional properties (only id, without conditions, without enabled)
• Tests verify that missing optional properties default correctly (enabled defaults to false, ClientFilters is empty)

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
sdk/appconfiguration/Azure.Data.AppConfiguration/src/Models/FeatureFlagConfigurationSetting.cs	Updated required properties array to only include "id", making "enabled" and "conditions" optional for validation
sdk/appconfiguration/Azure.Data.AppConfiguration/tests/FeatureFlagConfigurationSettingTests.cs	Added 6 new tests covering parsing and modification scenarios for feature flags with optional properties

[Copilot]

Missing test coverage: There should be a test verifying that a feature flag with only id can roundtrip without modification. Currently, the CanRountripValue test doesn't include test cases for minimal feature flags (e.g., {"id":"my feature"}).

Consider adding test cases to CanRountripValue or creating a new test that verifies:

var featureFlagValue = "{\"id\":\"my feature\"}";
var featureFlag = new FeatureFlagConfigurationSetting();
featureFlag.Value = featureFlagValue;

using var expected = JsonDocument.Parse(featureFlagValue);
using var actual = JsonDocument.Parse(featureFlag.Value);
Assert.IsTrue(_jsonComparer.Equals(expected.RootElement, actual.RootElement));

This would ensure that reading and serializing without modification preserves the original minimal JSON structure.