fix: Match TextBox.VerticalContentAlignment with Windows

[Youssef1313]

GitHub Issue (If applicable): closes #4502, closes #14705.

This is a revert of #4180

PR Type

What kind of change does this PR introduce?

What is the current behavior?

What is the new behavior?

Copilot Summary

🤖 Generated by Copilot at 5dd22d4

This pull request fixes a layout bug in TextBox controls and adds a unit test to verify the fix. It also improves the XAML loading logic by using .NET 7.0 source generators and a helper method LoadXaml.

PR Checklist

Please check if your PR fulfills the following requirements:

• 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)
• Validated PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Associated with an issue (GitHub or internal) and uses the automatic close keywords.
• Commits must be following the Conventional Commits specification.

Other information

Internal Issue (If applicable):

[Youssef1313]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[Youssef1313]

There is a problem on Skia where the native Gtk.Entry (shown only on focus), has the text centered vertically, and Gtk.Entry provides no way to change this behavior.

So:

• Existing behavior on Skia: On both focused & unfocused state, the text is centered vertically.
• New behavior on Skia: On focus, it's centered vertically. On unfocus, the text is top-aligned.
• Windows behavior: Text is top-aligned.

So while this PR gets closer to Windows behavior on Skia, I think it could be considered worse because of the inconsistency between focused and unfocused states.

[Youssef1313]

I guess @ramezgerges work will probably help unblock this. Let's see :)

[MartinZikmund]

@Youssef1313 I think the new behavior is acceptable - it will work properly with rendered TextBox and it works well with WPF

[Youssef1313]

@MartinZikmund Yup it should work well with the new TextBox implementation, but not the old one which is still the "default":

uno/src/Uno.UI/FeatureConfiguration.cs

Line 505 in efa47a5

public static bool UseOverlayOnSkia { get; set; } = true;

[MartinZikmund]

@Youssef1313 but that is the default only for now and will "change" soon, and WPF works fine so I don't see this as a big issue

[MartinZikmund]

@Youssef1313 I think this can be revived now after 5.2

[Youssef1313]

Yup. Sorry forgot about it earlier

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-13810/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-13810/index.html

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-13810/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-13810/index.html

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-13810/index.html

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-13810/index.html

[MartinZikmund]

Ready to be merged!