Debug Printf just before VK_DEVICE_LOST

Hi, Debug Printf is a very useful feature. In [documentation](https://github.com/KhronosGroup/Vulkan-ValidationLayers/blob/main/docs/debug_printf.md) there is no mention on behavior in case of VK_ERROR_DEVICE_LOST.

I think that having opportunity do insert Printf in failing shader would be an even better debug tool.
Maybe this could be enabled if `Printf buffer` mentioned [here](https://www.lunarg.com/wp-content/uploads/2021/08/Using-Debug-Printf-02August2021.pdf) was allocated optionally with [VK_MEMORY_PROPERTY_DEVICE_UNCACHED_BIT_AMD ](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VK_AMD_device_coherent_memory.html)?

Start with docs/debug_printf.md and the linked Printf buffer and VK_AMD_device_coherent_memory references; determine the current behavior of debug printf when VK_ERROR_DEVICE_LOST occurs. Done should be an agreed, reproducible behavior for printing from the failing shader, with the resulting behavior documented.

Written by the indexing model from the issue text.