IgnoreMissingFeatureFilters Option Should Not Throw For RequirementType.All

[rthomas-rdm]

Problem:
FeatureManagementOptions.IgnoreMissingFeatureFilters when true will throw if a feature has RequirementType.All set.

This implementation is extremely limiting as it prevents a global level option from being specified and used for requirement type Any features if a single feature of any number of potential features uses requirement type All.

Proposed Solution:

• Remove the throw condition linked above, and allow the option to be specified even if some features use RequirementType.All
• Update this IF condition instead to to be if (!_options.IgnoreMissingFeatureFilters || featureDefinition.RequirementType == RequirementType.All) { .. }

[jimmyca15]

It looks like there was a concern when adding the capability to require all feature filters to enable a feature that there may be confusion on how that would work with IgnoreMissingFeatureFilters.

I'm not quite clear why that's the case. I think it's clear that if there is a missing feature filter and requirement type 'all' is used, the feature would be considered disabled.

I don't see a problem to lift the restriction.

[jimmyca15]

In offline review there was agreeance that we can treat features that have requirement type all, and a missing filter, as a disabled feature.