Weird enter in closing when formatting XAML TextBlock

[JochemPalmsens]

Input:

    <TextBlock Foreground="DarkGray">
I saw the sign. When I opened up my eyes, I saw the sign.
</TextBlock>

Output:

    <TextBlock Foreground="DarkGray">
I saw the sign. When I opened up my eyes, I saw the sign.
</TextBlock
    >

Expected behavior:

    <TextBlock Foreground="DarkGray">
        I saw the sign. When I opened up my eyes, I saw the sign.
    </TextBlock>

Note: this only happens when the opening block sets properties. I.e., when you remove the Foreground="DarkGray", the closing > is in the right place again. But that's not a correct solution

[belav]

Currently CSharpier treats whitespace as strict in all xml files. This is going to cause some weirdness because you'll end up with this staying as is.

<Root>
  <TextBlock Foreground="DarkGray">
This stays dedented because CSharpier doesn't want to add any whitespace to this text element
</TextBlock>
  <TextBlock Foreground="DarkGray">
This stays indented because CSharpier doesn't want to remove any whitespace from this text element
        </TextBlock>
</Root>

I created #1790 so that xaml formatting can be improved along with any other file types that don't need strict whitespace around text elements.

The purpose of the > being on a new line is so that it always lines up with the opening element. That came from prettier but it looks weird in most cases and CSharpier wasn't consistently breaking it to a new line. I got this case changed so it stays on the same line as the closing element.