Implement a window wrapper for the Wayland protocol

[Dawoodoz]

Some Linux systems do not support X11 but have Wayland instead, which is a leaner and more modern alternative to X11.

Due to the library's principle of being easy to compile even if some libraries are missing, one should be able to compile a program exclusively for X11 or Wayland, in case that certain developer libraries no longer exist when compiling in a distant future. One can however use header implementations for X11 and Wayland, so that different cpp wrappers can select combinations of window managers, for those who have access to both when building their program and want the application to select the best at runtime like most media layers do.

Image upload
Having multi-threaded image upload with double buffering like the X11 window wrapper would be a plus, but stability and correct visuals is the first priority. Performance can be optimized later, because window wrappers are entirely separate from application code.

Fullscreen
Full screen should not force excessive control over the display with "native fullscreen", because this is not even a real thing after people stopped using CRT displays and will always crash on Raspberry Pi with fixed resolution screens. Trying to force an LCD to a different resolution will cause emulation of the resolution in either graphics drivers or a scaling processor in the display itself. This library already has upscaling functions built in to give full control over what the pixels look like, so just make it maximized, borderless and in front of everything else.

Input
Unicode character codes should be supported.

The point of keeping window backends minimal is to allow users to write their own 100 years from now after automatically porting the C++ code to a backwards compatible language, so having someone else perform this task would be a good test to see how long it takes and whether the intergation with BackendWindow is self explanatory or if a proper interface with detailed documentation is needed.