Vulkan: Check for vkSetDebugUtilsObjectNameEXT before using it

[JosJuice]

Fixes a crash that has been present on Android (and probably also macOS) since the merge of PR #10269.

This is my first time touching Vulkan, and I don't know if this is a "proper" solution. (Should we check for the existence of VK_EXT_debug_utils rather than checking the vkSetDebugUtilsObjectNameEXT function pointer directly?)

[iwubcode]

Yeah, I believe the way we've done this in the past is to introduce a new backend variable (something like supports_debug_names) and then set to the true for all backends except Vulkan. Vulkan would then check for the existence of VK_EXT_debug. The places you outlined would then check that backend object variable.

It's a lot of overhead though. I'd be fine with your solution as a temporary fix or a permanent solution.

To be fair, I don't know the Vulkan code base that well either (just started learning it), so we might check pointers as a solution as well.

[JMC47]

This is a simple solution that is easy to revert if we need a more robust solution.

I don't want to leave master broken for obvious reasons.

[chrisis123]

I can confirm this fixes the MacOS crash when starting a game for me (on an M1 Mac Book Pro) - I was just about to report this bug when I noticed this PR was merged

[brujo5]

fixed crash android to. thx