Treat VK_SUBOPTIMAL_KHR as VK_SUCCESS on Android.

[James2022-rgb]

Checklist

• Run cargo clippy.
• Run RUSTFLAGS=--cfg=web_sys_unstable_apis cargo clippy --target wasm32-unknown-unknown if applicable.
• Add change to CHANGELOG.md. See simple instructions inside file.

Connections
Addresses issue #3345.

Description
This PR makes is so that vkQueuePresentKHR's VK_SUBOPTIMAL_KHR is treated as VK_SUCCESS (i.e ignored and not logged) on Android.

On Android 10+, vkQueuePresentKHR returns VK_SUBOPTIMAL_KHR if the swapchain's VkSwapchainCreateInfoKHR::preTransform does not match the device's current orientation.
This is always the case in wgpu when the device orientation is anything other than the identity one,
because we unconditionally use VK_SURFACE_TRANSFORM_IDENTITY_BIT_KHR when creating the swapchain.

The assumption is that on Android, as discussed in the issue, VK_SUBOPTIMAL_KHR is only returned when the device's current orientation doesn't match VkSwapchainCreateInfoKHR::preTransform.

https://developer.android.com/games/optimize/vulkan-prerotation#detect_device_orientation_changes

The most reliable way to detect an orientation change in your application is to verify whether the vkQueuePresentKHR() function returns VK_SUBOPTIMAL_KHR.

The only code path that returns VK_SUBOPTIMAL_KHR in Android libvulkan's vkQueuePresentKHR implementation:
https://android.googlesource.com/platform/frameworks/native/+/master/vulkan/libvulkan/swapchain.cpp#2021

More in-detail description of the problem in the connected issue.

Testing
Tested on my Galaxy S20 Ultra 5G (Adreno 650), Android 10, that the log spam is no longer exhibited.

[teoxoy]

Thanks for the PR!

Looks good but there is one more spot where we should ignore this.
Search for acquire_next_image in the codebase.

[James2022-rgb]

Added a commit to ignore VK_SUBOPTIMAL_KHR for vkAcquireNextImageKHR as well!

[teoxoy]

LGTM