Enable wrapping of NavigationView/TabView like controls

This issue was discovered by Office folks when they attempted to wrap the XAML TwoPaneView. The issue occurs when you have this sort of arrangement:

[WrappedControl]
  [Component /]
  [etc]
[/WrappedControl]

In this situation, the WrappedControl runs layout in XAML which flexbox has no knowledge of. Inside the WrappedControl are react-native components which need flexbox to layout correctly. This doesn't currently work because flexbox is "stomping over" the properties that XAML is supposed to be in control of.

We know of several WinUI controls that behave similarly to TwoPaneView (NavigationView and TabView). So this will be a general problem moving forward if we want to wrap those types of controls.

There does appear to be a way to resolve the conflict - we'd need to let XAML participate in the overall layout process and override flexbox when necessary. Note that this solution would need to take the upcoming Fabric change into consideration - in that world, layout is running off of the UI thread, so letting XAML override becomes more difficult.

This issue is tracking solving this general problem.

Start by tracing how wrapped XAML controls and React Native flexbox participate in layout, using the TwoPaneView arrangement described in the issue. Compare the requirements for NavigationView and TabView, then account for Fabric layout running off the UI thread. Done means these controls can wrap React Native children without XAML-controlled properties being overwritten.