fix(windows): prevent crash on app exit caused by WinRT COM release d…

[Y-PLONI]

…uring DLL unload

Static WinRT/Composition objects (ICompositor, IDispatcherQueueController, GraphicsContext, RoHelper) were held in static smart pointers (winrt::com_ptr, std::unique_ptr, std::shared_ptr). Their destructors called Release() and RoUninitialize() during DLL_PROCESS_DETACH, after the WinRT DLLs had already started unloading, triggering RaiseFailFastException in KernelBase.dll and causing Windows Error Reporting to appear on exit.

Changes:

• Convert all four static WinRT/COM resource pointers to raw pointers so no RAII destructor runs Release() or RoUninitialize() at static-destruction time; the OS reclaims them at process exit instead.
• Add instance_count_ (protected by shared_resources_mutex_) to track the number of live InAppWebViewManager instances and trigger cleanup only when the last one is destroyed.
• Add detachSharedResourcesForShutdown() which nulls all raw pointers under the mutex (without delete/Release) and returns the dispatcher queue controller for subsequent use.
• Add shutdownDispatcherQueue() which calls ShutdownQueueAsync() outside the mutex and intentionally leaks both the IAsyncAction and the controller as process-lifetime objects, avoiding any Release() race with WinRT teardown.
• Remove the earlier AddRef() workaround on ICompositor, which did not actually prevent the crash.
• Replace the std::unique_ptr/shared_ptr allocations of RoHelper and GraphicsContext with raw new, consistent with the process-lifetime-leak design for all shared resources.

Fixes: #2733

Connection with issue(s)

Resolve issue #???

Connected to #???

Testing and Review Notes

Screenshots or Videos

To Do

• double check the original issue to confirm it is fully satisfied
• add testing notes and screenshots in PR description to help guide reviewers
• request the "UX" team perform a design review (if/when applicable)