VideoConfig: Add flag for whether the system supports setting object names

[OatmealDome]

Basically, the proper version of #10342.

A flag has been added to VideoConfig: bSupportsSettingObjectNames. This is now checked before calling glObjectLabel in the OpenGL backend and vkSetDebugUtilsObjectNameEXT in the Vulkan backend.

For the OpenGL backend, support is only set if on OpenGL >4.3 or OpenGL ES 3.2. This fixes a crash when using the OpenGL backend on macOS, the Android Emulator, and probably some other devices.

For the Vulkan backend, support is only set if the VK_EXT_debug_utils extension was loaded correctly. In addition, a bug has been fixed where vkSetDebugUtilsObjectNameEXT was loaded as if it were a device function. It is actually an instance function. (This caused Dolphin to fail when loading the function from MoltenVK.)

For the Direct3D backends, support is assumed because I haven't heard of any crashing related to this.

[Pokechu22]

You're missing includes for VideoCommon/VideoConfig.h in all of the Vulkan files (probably one of the other Vulkan files includes it, so it doesn't cause issues, but you should add the include anyways)

[OatmealDome]

Fixed, thanks.

[Pokechu22]

You're only setting bSupportsSettingObjectNames to true for D3D11; VideoBackends/D3D/D3DMain.cpp is for D3D11 while the D3D12 equivalent is VideoBackends/D3D12/VideoBackend.cpp.

Also, to make sure, AddExtension(VK_EXT_DEBUG_UTILS_EXTENSION_NAME, false) returning true implies that vkSetDebugUtilsObjectNameEXT is non-null, right?

[OatmealDome]

Fixed.

And, yes, I believe so. Otherwise, the driver would be in violation of the spec.