Vulkan UPDATE_AFTER_BIND usage Unsound

[cwfitzgerald]

Description

Currently we use UPDATE_AFTER_BIND to allow us to raise the limits on vk/intel/windows of images and buffers to reasonable levels (1600 -> 1,000,000).

This is unfortunately unsound as if a descriptor set has any dynamic offsets in it, it cannot be labeled as update after bind.

We have two options:

• Explicitly add UPDATE_AFTER_BIND-ness to the api (under a different name)
• Disable the UPDATE_AFTER_BIND workaround entirely.

Because we are going to be switching to DX12 soon, and this only affects windows/intel drivers not linux/intel, we should just scrap the workaround.