[Windows] Add WindowsBatchPropertyMapper to save unnecessary work when initializing views

[MartyIX]

Description of Change

This PR is based on the idea that for each view, many MapTranslation* methods are called but the they are called for no good reason because the operation is always the same. So in effect, there are many unnecessary interop calls which are costly.

The implementation is based on https://github.com/dotnet/maui/blob/c1566589d1794e5adcbcf2e93bd77fc85f859253/src/Core/src/Handlers/View/AndroidBatchPropertyMapper.cs (basically a copy).

Performance impact

• MAIN 1724527142..speedscope.MAIN.json
• PR 1724526920..speedscope.PR.json

Issues Fixed

Contributes to #21787
Replaces #21818

[dotnet-policy-service]

Hey there @MartyIX! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[PureWeen]

My gut here is that I'm still not a big fan of the Batching concept in general. I think it causes mappers to act in an unexpected way because now these mappers don't fire at all during the first pass. We've had a number of issues where we've put setup code into a mapper thinking it'll init with that property and then it never runs except for on updates.

I think a mechanism of defaults would make the most sense

Ideally, we'd have some mechanism where the mapper fires, but we don't pay the cost of interop.

Ideally the translation paths are just smart enough to know they don't need to fire an update.

Like, I'd almost rather see us just copy paste something into all these mappers that's like

if (IsInitialRun)
return;

versus trying to be too clever in a way that's kind of unexpected

[MartyIX]

Like, I'd almost rather see us just copy paste something into all these mappers that's like

if (IsInitialRun) return;

This PR #23987 does that.