VK_EXT_debug_report is not enabled when built

Reproduction steps:
1. Open the attached project "ReproProj" with Android platform
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Select Vulkan API in Edit > Project Settings > Player
4. Install and open Android LogCat
5. Build and Run
6. Use RenderDoc to capture a frame
7. Observe the Debug Markers shown in RenderDoc
8. If no custom debug markers are visible then run these adb shell commands:
    "adb shell cmd gpu vkjson | grep -E 'VK_EXT_debug_report|VK_EXT_debug_utils'"

Expected result: Custom debug markers are visible in RenderDoc when VK_EXT_debug_report or VK_EXT_debug_utils is supported
Actual result: Custom debug markers are NOT visible in RenderDoc when VK_EXT_debug_report or VK_EXT_debug_utils is supported

Reproducible with: 2022.2.2f1
Not reproducible with: 2021.3.29f1, 2022.3.8f1, 2023.1.10f1, 2023.2.0b6, 2023.3.0a3

Testing environment: Windows 10 Enterprise 21H2

Reproducible on:
----------, Samsung Galaxy S22 (SM-S901U), Android 12, CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno (TM) 730

Not reproducible on:
----------, Samsung Galaxy Z Fold2 5G (SM-F916B), Android 11, CPU: Snapdragon 865 SM8250, GPU: Adreno (TM) 650
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650