Add support for multiple error handling strategies

[yakovmanshin]

In addition to replacing an unsuccessfully resolved value with defaultValue, FeatureFlag should be able to pursue additional strategies, such as:

• calling a custom closure (something like (FeatureFlag, Error) -> Value);
• returning wrappedValue as optional;
• re-throwing the resolver error;
• etc.