Persistent buffer maps were already used by the texture cache, this extends their usage for the buffer cache.

In my testing, using the memory maps for uploads was slower than the existing "ImmediateUpload" path, so the memory map usage is limited to downloads for the time being.

vulkan_device: Enable VK_KHR_push_descriptor on newer ANV

texture_cache: process aliases and overlaps in the correct order

shader_recompiler: fix copy-paste error

Add a 5ms tiemout to the DSP processing wait

input_common: Implement amiibo writing

Don't exit when using "-u" option in yuzu-cmd

video_core: don't garbage collect during configuration

Add short "-u" option for yuzu_cmd.

The -u short option was documented but not implemented in yuzu_cmd.
The same long option --user worked before.

service: nfc: Remove encryption key requirement

Texture cache: revert wrong acceleration assumption

Texture Cache Util: Fix block depth adjustment on slices.

video_core: tune garbage collection aggressiveness

k_memory_block_manager: remove auditing calls

video_core: add ASTC recompression

vk_master_semaphore: Move fence wait on separate thread

renderer_vulkan: barrier attachment feedback loops

Limit device access memory for integrated devices to 4 GB

input_common: Map motion with relative values not absolute ones

Hardly limiting the device access memory to 4 GB for integrated vulkan devices here. This works for the Steam Deck in order not to go above 4 GB VRAM usage any more (above this value the likelihood to crash when the RAM exceeds 12 GB as well raises).

But there will be perhaps a detection mechanism necessary for detecting the real memory limit for integrated vulkan devices. Those likely might have small limits anyway, but what about integrated GPUs on machines with > 16 GB RAM, aka larger amounts ?

externals: update cubeb (again)

input_common: Fix pro controller amiibo support