Upgrade WindowsAppSDK dependency version

Description

In regards to the issue relating to the WebView2 control freezing when typing too fast: https://github.com/dotnet/maui/issues/12361

The issue has been fixed in a newer dependency version of WindowsAppSDK. Can MAUI please upgrade the references as manually specifying the PackageReference (<PackageReference Include="Microsoft.WindowsAppSDK" Version="1.2.230313.1" />) results in problems building with the following errors:

error NU1102: Unable to find package Microsoft.NETCore.App.Runtime.Mono.win-arm
error NU1102: Unable to find package Microsoft.NETCore.App.Runtime.Mono.win-arm64

Along with this error when attempting to publish via the CLI:

C:\Users\Kieran Devlin\.nuget\packages\microsoft.windowsappsdk\1.2.230313.1\buildTransitive\Microsoft.UI.Xaml.Markup.Co
mpiler.interop.targets(559,9): error MSB3073: The command ""C:\Users\Kieran Devlin\.nuget\packages\microsoft.windowsapp
sdk\1.2.230313.1\buildTransitive\..\tools\net5.0\..\net472\XamlCompiler.exe" "obj\release\net7.0-android\\input.json" "
obj\release\net7.0-android\\output.json"" exited with code 1. [C:\Users\Kieran Devlin\Documents\git\sources\App\..\App.csproj::TargetFramework=net7.0-android]

Steps to Reproduce

1. Specify the dependency version that fixes the referenced problem (<PackageReference Include="Microsoft.WindowsAppSDK" Version="1.2.230313.1" />)
2. Build once (the first build seems to work fine)
3. Build again, this build & all subsequent builds will fail.

Link to public reproduction project repository

N/a

Version with bug

7.0 (current)

Last version that worked well

7.0 (current)

Affected platforms

Android, Windows, I was not able test on other platforms

Affected platform versions

N/a

Did you find any workaround?

No response

Relevant log output

No response

[jfversluis]

Yeah I would assume people would want this as a service release for .NET 7?

@mattleibow ?

[KieranDevvs]

This is because you’re referencing it also in the android and ios app. If you reference it like this, it will work (only for Windows!)

While this may be a temporary work around, Id still like to see the framework take on the upgrade rather than delegating it to users.