feat: Add doNotActivate parameter to NavigateAsync method from Navigation Extensions

[xperiandri]

GitHub Issue (If applicable): closes #2381

PR Type

What kind of change does this PR introduce?

• Feature

What is the current behavior?

Window is always activated as soon as possible

What is the new behavior?

Window is activated either as soon as possible or right after the host is started (all hosted services completed)

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

[nickrandolph]

@xperiandri can you provide more context on the scenario you're trying to get to work?

[xperiandri]

OpenIddict Client starts a hosted service to determine protocol activation, redirect it and close the app.
With you current logic the second instance of the app manages to activate the window before the app exited. It causes a window to blip and close.
My modification allows to prevent that if necessary

[nickrandolph]

ok let me double check this next week - I thought we had a mechanism that would ensure some services are started before activation (eg localization from recollection).
If we do want to provide this, we'll possibly look at providing it as a registration on the DI, rather than as an argument to the app builder.
Thanks again for this suggestion!

[xperiandri]

I need this behavior, please

[xperiandri]

And I would prefer ability to just plug OpenIddict Client and it worked then declaring some additional services, implement some additional interfaces, etc.

[carldebilly]

That's odd using a double negative like that. That's confusing.

[nickrandolph]

@xperiandri the interface I was thinking of is the IStartupService, which will effectively block activation until it returns. You can register this service in order to block activation.
I'd like to explore what we can do to make it eaiser to just "plug OpenIDdict client" and leverage the authentionservice.

[xperiandri]

Sounds like a good idea in general.
The only question is how to make https://github.com/openiddict/openiddict-core/blob/dev/src/OpenIddict.Client.SystemIntegration/OpenIddictClientSystemIntegrationActivationHandler.cs become IStartupService

Inherit from it, remove registration as IHostedService from DI and register as IStartupService?

Kevin sealed OpenIddictClientSystemIntegrationActivationHandler, probably we can ask to unseal