There is a bug on Intel's blob driver where it fails to properly build a
vertex array object if it's not bound even after creating it with
glCreateVertexArrays. This workaround binds it after creating it to
bypass the issue.

service/vi: Correct reported dimensions from IApplicationDisplayService's GetDisplayResolution()

Return no application area when games try to open an application area

Proper no message handling for AM::PopMessage

Within the actual service, it makes no distinguishing between docked and
undocked modes. This will always return the constants values reporting
1280x720 as the dimensions.

Removed pulse event type

Pulse is considered a hack and nothing should be using it. We should completely remove it

service/vi: Minor updates and corrections to the DisplayInfo struct

Fixed botw deadlock due to incorrect event signal type

This will prompt CreateApplicationArea

When we have no messages, we should be returning an error code.

Port citra-emu/citra#4412: "CONTRIBUTING.md: migrate to the wiki"

Upon investigating the issue with #1878, I found that games are the ones who handle the vsync event resetting and not us.

service/vi: Implement OpenDefaultDisplay in terms of OpenDisplay

service/vi: Implement SetDisplayEnabled()

qt: Add setting to prompt for user on game boot

qt: Use ProfileSelectionDialog when selecting user for save data

This IPC command is simply a stub inside the actual service itself, and
just returns a successful error code regardless of input. This is likely
only retained in the service interface to not break older code that relied
upon it succeeding in some way.

service/vi: Log more information where applicable

In many cases, we didn't bother to log out any of the popped data
members. This logs them out to the console within the logging call to
provide more contextual information.

Internally within the vi services, this is essentially all that
OpenDefaultDisplay does, so it's trivial to just do the same, and
forward the default display string into the function.

gl_rasterizer_cache: Texture view if shader samples array but OGL is not

Based off RE, it appears that almost all display types seem to use
1920x1080 except for a few (null display, edid display).

It appears that the two members indicate whether a display has a bounded
number of layers (and if set, the second member indicates the total
number of layers).

Port citra-emu/citra#4187: "Qt/Configure: Use sidebar to divide tabs into smaller groups"

yuzu: Fix truncation warnings within UI code

core/kernel: Remove unnecessary inclusions

The QPixmap API expects an unsigned int.

Gets rid of a few unnecessary header dependencies in some source files.

arm_interface: Minor cleanup

kernel/svc: Sanitize core and priority masks within CreateThread

externals: Update fmt to 5.3.0

This is a bounds check to ensure that the thread priority is within the
valid range of 0-64. If it exceeds 64, that doesn't necessarily mean
that an actual priority of 64 was expected (it actually means whoever
called the function screwed up their math).

Instead clarify the message to indicate the allowed range of thread
priorities.

Now that we handle the kernel capability descriptors we can correct
CreateThread to properly check against the core and priority masks
like the actual kernel does.

Makes them consistent with their kernel capability counterparts.

Rather than use a switch here, this can be collapsed into a simple range
check, which is a little easier on the eyes.