Add support for configuring WebViewSettings via DI

[javiercn]

Adds support for configuring the Development tools via a settings object registered in DI.

A few things to note:

• There are new top-level extension methods Add<<Maui|Wpf|WindowsForms>BlazorWebView that are the entry point on each flavor and perform all registrations necessary on the DI container.
• The BlazorWebViewSettings is Settings and not Options because Maui by default doesn't support the Options pattern.
  • For this reason, the object is passed directly instead of using a callback as in more "idiomatic" ASP.NET Core extension methods.
  • The BlazorWebViewSettings is shared source a cross all platforms. Ideally this would have been defined in the abstract component package, but we already shipped that and we can't change it.
• We use a global object in DI instead of on a per webview basis because some options are only configurable globally (like DevelomentMode in Android) and we expect in most cases to only host one WebView at a time.
  • We can revisit this in the future if we detect that many people want to have multiple webviews with different settings associated with them.

[TanayParikh]

This looks great! Just some minor comments.

I believe I'll be able to leverage this to support DETAILED_ERRORS via #4441!

[Eilon]

@PureWeen FYI we're adding an overload here for handler registration that goes off of IServiceCollection because in some Blazor scenarios that's all we have access to.

[javiercn]

Good catch, I forgot to point it out.

[Eilon]

🥳

[Eilon]

Looks good to me. I think overall this API is cleaner and easy to use.

[SteveSandersonMS]

Awesome, thanks for handling all the feedback