Fixes #388 SizerBase Orientation Property

[michael-hawker]

Fixes #388

• Updates to WASDK 1.3 (resolves quirky/jumpy behavior on WindowsAppSDK due to Manipulation event bug in platform - see WinUI3 - ManipulationStarting Event only occurs on first touch -> e.Container Property is null in following manipulation events microsoft/microsoft-ui-xaml#6847)
• Removes Mouse Extension from XAML Template and does in code-behind as to remove the need to set the Cursor property directly via binding
  • By setting the Cursor DependencyProperty we were losing our detection mechanism, now if it's set it's an explicit override, otherwise we use our logic based on Orientation property
• Also, switches to new CommunityToolkit.*.Extensions Dependency vs. old copies of Tree helpers
• Fixes some doc typos
• Bumps version, tested locally on UWP, WASDK, and Uno.UI/WASM

Just need to see if anything breaks in the CI due to the update to the WASDK... Otherwise, should be good to go and will help with #418's next step. 🎉

Glad to finally get this stuff resolved, this has been in the back of my mind for a while now. The new SizerBase is now above-and-beyond what we currently have in WCT. Just needs some future modern magic to discuss with @niels9001 as the final frontier (as a separate PR in the future).

[michael-hawker]

Looks like the extensions broke in the tests with the flip or something...

Ah, it's the underlying update to the tooling sub-module with the flip to the extensions I needed to include in here.

Thinking I'll just add CommunityToolkit.WinUI back to the GlobalUsings_Tests.cs for now then?

[michael-hawker]

Hmm, WinUI 3 failed to build do to namespace conflict... Wonder if from global using I added in tooling? Or could be the other components references to the older package, trying to change that, though Shimmer uses the animation package which has an indirect dependency... so not sure if that's still going to be trouble. This is a bit complex here with the old vs. new incompatibility with the namespace change... hmm... Would make sense that the WinUI 2 build works here as it was a completely different root to the namespace anyway.

[michael-hawker]

Think going to have to bring other helpers over, as there's the CompositionTargetHelper and WeakEventListener used in here too... hmmm

[michael-hawker]

Thinking about it more, we probably want to wait in using the new unified packages until more of them are setup. Otherwise, they'll start forcing folks to also use them over the 7.1.x packages when trying to use Labs components, don't think we're quite ready for that...

Will merge Niels' new style PR in first after I test on Win 10 - michael-hawker#2 - and then untease/revert back to the 7.x extension usage.

[michael-hawker]

Now that CommunityToolkit/Windows#26 is merged in the new repo, we can just close this, it has the same fix as here. Should probably remove SizerBase from this repo now.