Add vertical alignment support to WrapPanel

[vgromfeld]

Describe the bug

The WrapPanel control does not respect the required vertical alignments of its children controls.

Steps to Reproduce

Steps to reproduce the behavior:

1. Use the following code

<controls:WrapPanel
    Orientation="Horizontal">
    <Border Width="32" Height="32" Background="Blue" VerticalAlignment="Center" />
    <TextBlock
        VerticalAlignment="Center"
        Text="Some random text" />
    <Rectangle
        Width="1"
        Height="8"
        Margin="8,0"
        VerticalAlignment="Center"
        Fill="{ThemeResource SystemBaseHighColor}" />
    <Button
        VerticalAlignment="Center"
        Content="Button 2" />
    <Rectangle
        Width="1"
        Height="8"
        Margin="8,0"
        VerticalAlignment="Center"
        Fill="{ThemeResource SystemBaseHighColor}" />
    <HyperlinkButton
        VerticalAlignment="Center"
        Padding="0"
        Content="Button 2" />
</controls:WrapPanel>

Expected behavior

The panel should vertically align the children based on their vertical alignment values.

Screenshots

Actual behavior

Expected behavior (using a stack panel)

[ghost]

Hello vgromfeld, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[Kyaa-dost]

Thanks, @vgromfeld for highlight this. Padding has been a known issue similar to #3257 and #3416

[skendrot]

What other Panels offer VerticalContentAlignment and HorizontalContentAlignment? StackPanel does not, and Grid does not. Why offer it for the WrapPanel?

[michael-hawker]

Thanks @skendrot I agree that we should just be inspecting the child's alignment property in the layout pass of the panel vs. a separate property, I commented more in the pr here.

The bug itself here about the property currently not being respected is a valid concern still though. I think we can just pivot the solution a bit.