v3.2.3

• Reverted the VK_ERROR_INITIALIZATION_FAILED fix from v3.2.1. Unfortunately that change led to multiple reports of encodes getting corrupted, coupled with a new error: VK_ERROR_DEVICE_LOST. I have been unable to reproduce this outside of running a real encode, which I'd rather not do since waiting over an hour to test possible fixes is a terrible experience. While the fix is/was very much desired, it's hard to justify keeping it if it is going to hurt overall stability. v3.2.1 and v3.2.2 are still available for those that really want a VK_ERROR_INITIALIZATION_FAILED solution and are willing to risk a corrupted encode.
• Updated libplacebo to 5ba1376.