frame-buffer: Only destroy depth image if created by gulkan
Now that an existing VkImage for depth can be passed into gulkan, we should not unconditionally call vkDestroyImage for it.
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Now that an existing VkImage for depth can be passed into gulkan, we should not unconditionally call vkDestroyImage for it.