Make setting LogicalPosition and LogicalSize values generic over Into conversions

[nvzqz]

This allows for doing:

let window: Window = ...;
window.set_outer_position((100, 200));

---

• Tested on all platforms changed
• Added an entry to CHANGELOG.md if knowledge of this change could be valuable to users
• Updated documentation to reflect any user-facing changes, including notes of platform-specific behavior
• Created an example program if it would help users understand this functionality
• Updated feature matrix, if new features were added or implemented

[goddessfreya]

Can this be rebased off the eventsloop-v2 branch?

[nvzqz]

Checks seem to be failing since I changed the base branch on GitHub after I pushed the new changes.

[aloucks]

It couldn't be merged before you changed the destination branch. Try pushing another commit to trigger the build again.

[goddessfreya]

Please make this compile on linux.

[Osspial]

This PR seems to have a lot of overlap with #895, which does more comprehensive changes to the DPI API.

[nvzqz]

The intention of this PR is to make it possible to just convert from tuples. Since logical values are what are usually used, it may make sense to implement From<(u32, u32)> and From<(f64, f64)> for Size that constructs a Size::Logical. Likewise for Position.

[Osspial]

I'm not inclined to implement that conversion, since that implies that there's a "right" way to convert between an untyped coordinate pair and a physical or logical coordinate pair. However, there isn't - one of the reasons for switching to that design is explicitly to de-opinionate Winit in regards to physical/logical coordinate space. Logical and physical coordinate each have their use-cases, and it's been demonstrated that asserting a one-size-fits-all solution will only irritate our users. Enabling (f64, f64) and (u32, u32) conversions is a less harmful echo of that ideology, and I feel it's easier to just not take a stance there at all.

[Osspial]

With that stated, I'm going to close this PR