Code Quality: Use WindowContext instead of AppModel

[0x5bfa]

AppModel was leftover from UWP, removed and replaced with WindowContext which can be DI'd.

[yaira2]

For testing, we should test one or two of the properties and ensure they are updated correctly. For example, we should ensure that IsCompactOverlay and IsPasteEnabled are correctly updated when the state changes.

[0x5bfa]

Sorry for making extra change while you finished review.
I wanted to make sure reduce App.WindowContext reference.

[0x5bfa]

Now, ready to be merged

[0x5bfa]

I'm not sure why it's fail again and again since I can build, deploy and see that the window successfully opens without any crash.

It's failing here:

Files/tests/Files.InteractionTests/Tests/FolderTests.cs

Line 54 in cc0a770

TestHelper.InvokeButtonById("InnerNavigationToolbarNewButton");

Can you check if you can open New... button on your end?

The merge-base changed after approval.

[yaira2]

Try rebasing the branch from main.

[yaira2]

@0x5bfa can you try forking these changes to another branch to see if that fixes the CI issues?

[0x5bfa]

Sure.