Bug: SynchronizationContext is not set for secondary views in a UWP app

Description

SynchronizationContext.Current is null for any secondary application views (created by CoreApplication.CreateNewView()) in a UWP app using CsWinRT. This means after awaiting most async methods from the UI thread of a secondary view, trying to set a control property crashes due to being on the wrong thread. It seems the workaround is to use the Windows.System.DispatcherQueueSynchronizationContext type provided by CsWinRT as follows when setting up the view. However, I couldn't find this documented anywhere.

 await newView.Dispatcher.RunAsync(CoreDispatcherPriority.Normal, () =>
 {
     var context = new DispatcherQueueSynchronizationContext(DispatcherQueue.GetForCurrentThread());
     SynchronizationContext.SetSynchronizationContext(context);
     //...

Is this a bug or is it a necessary workaround that needs documenting? This just worked by default with the old .Net Native toolchain.

PS the SynchronizationContext for the main thread is correctly set to Windows.System.DispatcherQueueSynchronizationContext in the generated main function.

Steps To Reproduce

See description

Expected Behavior

No crash

Version Info

CsWinRT 2.2, Windows 25H2, UWP.

Additional Context

No response

Start by reproducing the secondary-view setup described with CoreApplication.CreateNewView() on CsWinRT 2.2, then compare its SynchronizationContext with the generated main function. Investigate DispatcherQueueSynchronizationContext and the await-to-control-property path; done means establishing whether CsWinRT should set the context automatically or documenting a confirmed workaround, with the crash no longer occurring.