Essentials fix DeviceDisplay and DeviceInfo

[PureWeen]

Description of Change

Convert over all of the static UWP static method calls to use PInvoke via the WindowHandle
Most of the code here is taken from

https://github.com/marb2000/DesktopWindow

The one unfortunate part of this code is the additional call from Maui.Core into Essentials through IVT. Taking from @marb2000 's examples the only way to react to the orientationchange/dpi change is by inspecting the windows messages. You can get pretty close by subscribing to the Change event on AppWindow but there are some edge cases (landscape to landscae flipped) where it looks like the Change event doesn't fire on AppWindow. Hopefully there will be some additional APIs added to WinUI down the road that let us sever this requirement.

PR Checklist

• Targets the correct branch
• Tests are passing (or failures are unrelated)
• Targets a single property for a single control (or intertwined few properties)
• Adds the property to the appropriate interface
• Avoids any changes not essential to the handler property
• Adds the mapping to the PropertyMapper in the handler
• Adds the mapping method to the WinUI, Android, iOS, and Standard aspects of the handler
• Implements the actual property updates (usually in extension methods in the Platform section of Core)
• Tags ported renderer methods with [PortHandler]
• Adds an example of the property to the sample project (MainPage)
• Adds the property to the stub class
• Implements basic property tests in DeviceTests

Does this PR touch anything that might affect accessibility?

• Does this PR introduce a new control? (If yes, add an example using SemanticProperties to the SemanticsPage)
• APIs that modify focusability?
• APIs that modify any text property on a control?
• Does this PR modify view nesting or view arrangement in anyway?
• Is there the smallest possibility that your PR will change accessibility?
• I'm not sure, please help me

If any of the above checkboxes apply to your PR, then the PR will need to provide testing to demonstrate that accessibility still works.

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).