[performance] all `PropertyMapper`'s set the same values over and over

[jonathanpeppers]

Description

A good example of this is:

maui/src/Core/src/Platform/Android/ActivityExtensions.cs

Lines 5 to 26 in 9a9537e

	internal static partial class ActivityExtensions
	{
	internal static Rect GetWindowFrame(this Android.App.Activity activity)
	{
	var bounds = PlatformInterop.GetCurrentWindowMetrics(activity);
	return activity.FromPixels(bounds);
	}
	internal static void UpdateX(this Android.App.Activity activity, IWindow window) =>
	activity.UpdateUnsupportedCoordinate(window);
	internal static void UpdateY(this Android.App.Activity activity, IWindow window) =>
	activity.UpdateUnsupportedCoordinate(window);
	internal static void UpdateWidth(this Android.App.Activity activity, IWindow window) =>
	activity.UpdateUnsupportedCoordinate(window);
	internal static void UpdateHeight(this Android.App.Activity activity, IWindow window) =>
	activity.UpdateUnsupportedCoordinate(window);
	internal static void UpdateUnsupportedCoordinate(this Android.App.Activity activity, IWindow window) =>
	window.FrameChanged(activity.GetWindowFrame());

But patterns like this are in many places currently in .NET MAUI.

The only place we've attempted to do something better is:

maui/src/Core/src/Handlers/View/AndroidBatchPropertyMapper.cs

Line 7 in 9a9537e

class AndroidBatchPropertyMapper<TVirtualView, TViewHandler> : PropertyMapper<TVirtualView, TViewHandler>

But ideally, a pattern could be adopted/invented for all platforms.

Public API Changes

Depending on what the new, invented pattern is. There may be public API changes, not sure.

Intended Use-Case

Improved performance for:

• Startup
• Creating new controls/views
• Scrolling data-bound CollectionView
• etc. etc.

[bcaceiro]

This should be on the top of the list for analysis, since may affects all platforms, performance etc.

[MartyIX]

@bcaceiro If you feel this issue is important, then please upvote it.