Fix: WithUseInterpretation() still triggers DynamicMethod on Xamarin.iOS AOT (SIGABRT)

[Copilot]

When Rules.WithUseInterpretation() is configured (intended for AOT platforms like Xamarin.iOS), DryIoc could still internally call Expression.Compile(preferInterpretation: true) as a fallback when the DryIoc interpreter failed for an expression. On Mono/AOT, this internally creates a DynamicMethod, causing PlatformNotSupportedException / SIGABRT — typically observed on second navigation in Xamarin.Forms apps.

Changes

• FactoryDelegateCompiler.CompileOrInterpretFactoryDelegate: When preferInterpretation = true, instead of falling back to Expression.Compile(), return a delegate that wraps the DryIoc interpreter directly. This eliminates all DynamicMethod / IL emit paths when UseInterpretation = true.

• Error.UnableToInterpretExpression: New error code with an actionable message thrown when the interpreter cannot handle an expression (e.g., ExpressionFactory with complex arbitrary expressions like Conditional that are not covered by the DryIoc interpreter). Previously this silently fell back to compilation, which is the wrong behavior on AOT platforms.

// Before: when interpreter failed, fell back to Expression.Compile() → DynamicMethod on Mono/AOT
return new FactoryDelegateExpression(expression).ToLambdaExpression()
    .Compile(preferInterpretation); // ← SIGABRT on Xamarin.iOS AOT

// After: wrap interpreter in a delegate; throw clear ContainerException if expression is uninterpretable
return r => Interpreter.TryInterpretAndUnwrapContainerException(r, expression, out var result)
    ? result
    : Throw.For<object>(Error.UnableToInterpretExpression, expression);

• GHIssue571 tests: Added tests covering:
  • Multiple scope open/close cycles (simulating repeated page navigation) to validate interpretation works correctly across scopes without triggering compilation.
  • Test_UnableToInterpretExpression_thrown_for_unsupported_expression_with_UseInterpretation: verifies that when an ExpressionFactory produces a Conditional expression (not handled by the DryIoc interpreter), a ContainerException(Error.UnableToInterpretExpression) is thrown instead of falling back to Expression.Compile() / DynamicMethod.

Behavioral note: On JIT platforms (Android, .NET Core), CompileOrInterpretFactoryDelegate(false) is unchanged — FEC + Expression.Compile() are still used when UseInterpretation = false. The only affected code path is the preferInterpretation = true branch.

[dadhi]

Why capturedExpr, why not use expression directly?

[Copilot]

Removed in 2aeaf03 - expression is already a local variable (reassigned from NormalizeExpression()) so capturing it directly works fine.

[dadhi]

Add the test which actually goes to this condition branch and throws this expression, with the complex Made.Of or someth not supported by DryIoc interpreter.

[Copilot]

Added Test_UnableToInterpretExpression_thrown_for_unsupported_expression_with_UseInterpretation in 2aeaf03. It uses ExpressionFactory with a Conditional (ternary) expression — ExprType.Conditional is not in the interpreter's TryInterpret switch, so it hits default: return false. With UseInterpretation=true, the fix throws ContainerException(Error.UnableToInterpretExpression) instead of falling back to Expression.Compile().