Fix StylusPlugIn OnStylusDown/Move/Up invoked on UI thread and called out of order

[lindexi]

Fixes #11103

Main PR

Description

See #11103

The stylusDevice.CriticalActiveSource may be null. And the stylusDevice.CriticalActiveSource will update from inputReport.InputSource. So that we directly use inputReport.InputSource will be safe and reasonable.

This PR can not 100% fix the #11103 , but this PR can alleviate the problem.

Customer Impact

Fix the out of roder issues.

Regression

None.

Testing

Test pass in my touch device.

And I build and publish my version to NuGet: https://www.nuget.org/packages/dotnetCampus.WPF.Resource/6.0.4-alpha07-test10

Risk

Normal. As description says, the stylusDevice.CriticalActiveSource will update from inputReport.InputSource in UI thread. We can directly use inputReport.InputSource in Stylus Input thread safely.

Microsoft Reviewers: Open in CodeFlow

[Copilot]

Pull Request Overview

This PR fixes an issue where StylusPlugIn methods (OnStylusDown/Move/Up) were being called out of order due to potential null reference issues with stylusDevice.CriticalActiveSource. The fix ensures thread safety by using inputReport.InputSource as the primary source, falling back to stylusDevice.CriticalActiveSource only when needed.

• Replace direct usage of stylusDevice.CriticalActiveSource with null-coalescing pattern using inputReport.InputSource

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}