Autosugest box unaligned text

Describe the bug The autosugest box’s placeholder and content text do not center-align vertically when indicated. Changing it to bottom doesn’t appears to work either.

Steps to reproduce the bug

Steps to reproduce the behavior: 1- Create a Autosugest box using the following boilerplate code:

	<Grid x:Name="ContentArea" Margin="{StaticResource MediumLeftRightMargin}">
		<Grid.RowDefinitions>
			<RowDefinition Height="Auto" />
			<RowDefinition Height="*" />
		</Grid.RowDefinitions>
		<!-- Top Bar Definitions -->
		<Grid Grid.Row="0" Margin="15">
			<Grid.ColumnDefinitions>
				<ColumnDefinition Width="2.5*" />
				<ColumnDefinition Width="1.5*" />
			</Grid.ColumnDefinitions>
			<!-- Search Box -->
			<StackPanel Grid.Column="0" Orientation="Horizontal" VerticalAlignment="Center">
				<AutoSuggestBox x:Name="SearchDownload" Width="475" Height="45"
				PlaceholderText="Find a downloaded item" QueryIcon="Find"
				VerticalContentAlignment="Bottom" HorizontalContentAlignment="Left"
				TextChanged="SearchDownload_TextChanged" QuerySubmitted="SearchDownload_QuerySubmitted" SuggestionChosen="SearchDownload_SuggestionChosen" />
			</StackPanel>
         </Grid>

Expected behavior The text should modify its centering relative to the control itself.

Screenshots

Version Info 2.4.3 recently updated but it didn’t solve it either. Used an older version (I think it was 2.2.1) and the problem existed there too, that’s why I updated the dependence.

NuGet package version: Microsoft.UI.Xaml 2.4.3

Windows app type:

UWP	Win32
Yes

Windows 10 version	Saw the problem?
Insider Build (xxxxx)
May 2020 Update (19041)
November 2019 Update (18363)	Yes
May 2019 Update (18362)	Yes
October 2018 Update (17763)
April 2018 Update (17134)
Fall Creators Update (16299)
Creators Update (15063)

Device form factor	Saw the problem?
Desktop	Yes
Xbox
Surface Hub
IoT

Additional context

[chingucoding]

@ranjeshj I think you can close this again since #4037 won’t revert the changes to AutoSuggestBox anymore.

[beervoley]

@OnlyOnePro @chingucoding Please have a look at this PR that addresses this issue