Refine the CmdPal launch and activation logic when opening a new app instance

[lei9444]

Summary of the Pull Request

This PR address #39376

Key changes:

1. Ensures RedirectActivationToAsync(args) is properly awaited using .GetAwaiter().GetResult() to preserve activation data.
2. Uses DispatcherQueue.TryEnqueue to safely handle UI thread execution and avoid COMException during window activation.
3. Addresses a race condition in Logger.InitializeLogger where multiple instances could trigger creation of unexpected log files. The root cause is that TextWriterTraceListener attempts to create a log file even if the target file is already in use, which results in a fallback file path prefixed with a GUID.

PR Checklist

• Closes: #39376
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated
• New binaries: Added on the required places
  • JSON for signing for new binaries
  • WXS for installer for new binaries and localization folder
  • YML for CI pipeline for new test projects
  • YML for signed pipeline
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

[Copilot]

Pull Request Overview

This PR refines the CmdPal launch and activation logic to address activation data preservation, COM exceptions during window activation, and a race condition in logger initialization.

• Ensures synchronous waiting on RedirectActivationToAsync to preserve activation data.
• Moves COM wrappers initialization ahead of redirection decision.
• Uses DispatcherQueue.TryEnqueue to safely invoke UI thread operations.

Comments suppressed due to low confidence (2)

src/modules/cmdpal/Microsoft.CmdPal.UI/Program.cs:116

• Consider handling potential exceptions within the DispatcherQueue callback to prevent silent failures if mainWindow.HandleLaunch(args) throws.

mainWindow.DispatcherQueue.TryEnqueue(() => {

src/modules/cmdpal/Microsoft.CmdPal.UI/Program.cs:101

• Blocking on an asynchronous call using GetAwaiter().GetResult() can potentially lead to deadlocks; please ensure this synchronous wait is safe in the current application context.

keyInstance.RedirectActivationToAsync(args).AsTask().GetAwaiter().GetResult();

[Copilot]

[nitpick] Consider adding an inline comment explaining why COM wrappers are initialized before the redirection decision to improve clarity.