Blazor Hybrid WebViewRenderer no-ops per-component render modes

[Copilot]

Blazor Hybrid WebViewRenderer no-ops per-component render modes

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Support per-page/component render modes in Blazor Hybrid WebView

Description

maui-blazor-web shared components can declare per-page/component render modes (for example InteractiveAuto) that work on web but currently throw in Blazor Hybrid because WebViewRenderer inherits the base Renderer fallback that rejects unsupported modes. This change makes WebView treat render modes as no-ops, matching Hybrid’s always-interactive execution model.

• Renderer behavior update

  • WebViewRenderer now overrides ResolveComponentForRenderMode(...) and always creates the requested component instance instead of throwing for render modes.
  • This aligns WebView behavior with Hybrid semantics and removes failures for components/pages using interactive render modes from shared RCLs.

• Regression coverage

  • Added a WebView unit test that renders a child component with RenderMode.InteractiveAuto set at the component callsite and verifies render flow completes successfully.

protected override IComponent ResolveComponentForRenderMode(
    Type componentType,
    int? parentComponentId,
    IComponentActivator componentActivator,
    IComponentRenderMode renderMode)
    => componentActivator.CreateInstance(componentType);

[javiercn]

This is a duplicate of another PR that I created a while ago.

[javiercn]

Closing as dupe of #65876