Some Essentials APIs crash when using multi-window

### Description

Most of the sensors (but some others) are using an incorrect way of marshalling the events to the main thread. They pick the active window, but this is incorrect because if you have multiple windows and then try update another window, there is a marshalling error.

### Steps to Reproduce

1. Create a new window on the default thread
2. Create a new window on a new thread
3. Start listening to accelerometer on both windows
4. Update a label on each window in the event
5. One window (the non-active window) will throw an exception

Start a new window in a new thread like this:

```cs
var thread = new Thread(() =>
{
Microsoft.UI.Xaml.Application.Start(async (p) =>
{
var dispatcherQueue = Microsoft.UI.Dispatching.DispatcherQueue.GetForCurrentThread();
var syncContext = new Microsoft.UI.Dispatching.DispatcherQueueSynchronizationContext(dispatcherQueue);
SynchronizationContext.SetSynchronizationContext(syncContext);

Application.Current.OpenWindow(new Window(new MultiWindowPage()));
});
});

thread.SetApartmentState(ApartmentState.STA);
thread.Start();
```

### Version with bug

Preview 14 (current)

### Last version that worked well

Unknown/Other

### Affected platforms

Windows

### Affected platform versions

All

### Did you find any workaround?

_No response_

### Relevant log output

_No response_

Start by tracing how Essentials APIs, especially the accelerometer, marshal events to the main thread in the multi-window scenario described. Reproduce the two-window setup using Application.Current.OpenWindow and verify that both windows can update their labels from sensor events without a marshalling exception.

Written by the indexing model from the issue text.