Fix for textures initialized with VkCopyMemoryToImage

[sasamiyatu]

Description

Currently, textures initialized using Vulkan 1.4 vkTransitionImageLayout and vkCopyMemoryToImage functions show up as black with 'Unknown previous layout' in RenderDoc captures. With these changes, these textures show up correctly with the correct layout in captures.

[baldurk]

This change is not correct as it stands, serialising vkCopyMemoryToImage will massively bloat memory usage while idle and although vkTransitionImageLayout is a smaller memory leak it will not cause any more calls to be serialised within the capture as the frame capture record is cleared before capture begins.

From what I can see possibly a needed change here is to ensure image layout tracking is updated when idle capturing, but without understanding the root problem I can't say. Can you please open a bug report following the template and provide a reproducible test case?

[sasamiyatu]

Thank you for your feedback. I did verify that these changes fixed the issue with the test case I had. I will open a bug report with a reproducible test case.