[Issue] Delete and compatibility issues with the Show method of IDialogService

[Coolkeke]

Why is there only ShowDialog in IDialogService in Prism. Avalonia, and why not keep the original Show method at the same time?
If considering multithreading, the Show method should not be removed. In Windows, there is a concept of information loop, and ShowDialog can achieve modal effects while blocking business code without blocking UI threads.
The ShowDialog in Prism. Avalonia currently does not meet the above requirements. In reality, what we see is still an asynchronous effect and the modal effect cannot block business code, which is not very ideal.
Have you considered compatibility optimization in the future

[Coolkeke]

If you have any other considerations, could you tell us about this design idea? We are currently giving a presentation on the Prism. Avalonia framework and exploring it, and we have found that there are related issues with the pop-up service. Are you interested? Let's discuss it together。
I am not very good at English, so I use translation tools to communicate with you. This may not be convenient, but I don't think it affects our technical discussion. As long as we are not having a voice conversation, we can basically complete the framework bug fixing work
@DamianSuess

[Coolkeke]

Is KnownDialogParameters really necessary?
In the process of exploration, I feel that the significance of existence is not very significant, and the vast majority can be solved by using additional properties. I see that the built-in parameters in the source code are given to solve certain functions.
Did the original developers of Prism build KnownDialogParameters to address and enhance certain features and achieve extension effects?