Changelog:

- **Breaking** All `check_buffer_access` and `check_image_access` functions now take an `UnsafeBuffer`/`UnsafeImage` and a `Range<DeviceSize>`.
- **Breaking** `UnsafeCommandBufferBuilder::pipeline_barrier` now takes a `DependencyInfo`. It will use `vkCmdPipelineBarrier2` if supported.

Like the previous PR, not many actual user-visible changes here. The major change here is that SyncCommandBuffer now tracks the state of resources as subranges too when building the command buffer or when checking for access. This means that the access state is tracked individually for each byte of a buffer and each subresource of an image, and pipeline barriers are applied to these subpieces instead of to the whole thing.

The buffer and image types themselves may not yet make full use of this capability; for example, an image view can select a subresource range from its parent image, but it's still treated in the command buffer as if it covers its whole parent. This is work for a future PR; the groundwork has been laid so the capability is now there. I'm happy to say that the texture_array example is working again, however.