[Wasm] Text measurement bug when ancestor contains a RenderTransform

[carldebilly]

GitHub Issue (If applicable): #808

Bugfix

Text measurement refactoring.

What is the current behavior?

Sometimes a TextBlock were wrapping even if the parent were provinding enough space to prevent it.

The problem was caused by a parent element containing a transform in the HTMLDOM. The cause
is directly in the spec itself:

https://www.w3.org/TR/css-transforms-1/

For elements whose layout is governed by the CSS box model, any value other than none
for the transform property also causes the element to establish a containing block for all
descendants. Its padding box will be used to layout for all of its absolute-position
descendants, fixed-position descendants, and descendant fixed background attachments.

BONUS: The investigations also revealed another one, never reported: a TextBlock width was hard limited to viewport width.

What is the new behavior?

This limitation is now used to remove any kind of [known yet] DOM ancestor constrains.
The parent element is now set to almost-infinite size to remove any size contention.

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

Internal Issue (If applicable):

• https://nventive.visualstudio.com/Umbrella/_workitems/edit/154814

[jeromelaban]

There's a rendering difference in SamplesApp.Windows_UI_Xaml_Controls.ListView.ListViewChangeHeight.png:

is that expected ?

[carldebilly]

@jeromelaban It is expected: