tu/kgsl: Fix patched Turnip for Adreno 830/840

[lfdevs]

Currently, the Turnip driver from the standard release (whose release title doesn't have the turnip- prefix) fails to work on most Adreno GPUs, and the possible error messages are as follows. This PR aims to fix this issue.

[Vulkan Loader] WARNING | LAYER: env var 'VK_INSTANCE_LAYERS' defined and adding layers "VK_LAYER_KHRONOS_validation"
[Vulkan Loader] ERROR | LAYER:  Layer "VK_LAYER_KHRONOS_validation" was not found but was requested by env var VK_INSTANCE_LAYERS!
[Vulkan Loader] WARNING | LAYER: env var 'VK_INSTANCE_LAYERS' defined and adding layers "VK_LAYER_KHRONOS_validation"
[Vulkan Loader] ERROR | LAYER:  Layer "VK_LAYER_KHRONOS_validation" was not found but was requested by env var VK_INSTANCE_LAYERS!
[Vulkan Loader] LAYER:          vkCreateInstance layer callstack setup to:
[Vulkan Loader] LAYER:             <Application>
[Vulkan Loader] LAYER:               ||
[Vulkan Loader] LAYER:             <Loader>
[Vulkan Loader] LAYER:               ||
[Vulkan Loader] LAYER:             <Drivers>
TU: info: TU_DEBUG=0x20003
TU: info: Created an instance
[Vulkan Loader] ERROR:          setup_loader_term_phys_devs: Call to 'vkEnumeratePhysicalDevices' in ICD /usr/lib/aarch64-linux-gnu/libvulkan_freedreno.so failed with error code -3
[Vulkan Loader] ERROR:          setup_loader_term_phys_devs:  Failed to detect any valid GPUs in the current config
vkcube: ./cube/cube.c:4153: demo_select_physical_device: Assertion `!err' failed.

[lfdevs]

Note

The driver built by this PR contains both patched Freedreno & Turnip, no need to install unpatched Turnip again.

Build artifacts: https://github.com/lfdevs/mesa-for-android-container/actions/runs/25629402080?pr=54#artifacts
It is worth mentioning that the directly downloaded file is a .zip archive, which needs to be unzipped once to get the .tar.gz installation package.

The vkcube test results are as follows:

Device	GPU	vkcube
REDMI K80 Pro	Adreno 830	✔️
Xiaomi Pad 6 Pro	Adreno 730	❌

Tips: When testing vkmark, it is recommended to add the parameter --winsys xcb, see: #51 (comment)

If vkcube fails to run, you can use the following environment variables to get detailed logs. This is very helpful for locating issues:

export VK_LOADER_DEBUG=all MESA_DEBUG=1 VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation TU_DEBUG=startup,log,perf,nir FD_RD_DUMP=enable