zink: add queue locking
sparse binds have to be processed synchronously with cmdbuf recording to avoid resource object desync in the vk driver, which means they have to be done in the driver thread instead of the flush thread. this necessitates adding locking for the queue since there is now a case when submissions occur in a different thread
fixes illegal multithread usage in KHR-GL46.CommonBugs.CommonBug_SparseBuffersWithCopyOps
cc: mesa-stable