Implicit same-parent VUs incorrect

Implicit same-parent VUs seem incorrect. E.g. `vkQueueSubmit` (resp. `VkSubmitInfo`) has:

> Each of the elements of `pCommandBuffers`, the elements of `pSignalSemaphores`, and the elements of `pWaitSemaphores` that are valid handles **must** have been created, allocated, or retrieved from the same `VkDevice`

That allows to only pass parameter that has the same parent, but still allows the parent to be distinct from the dispatchable parameter of the command (the `queue`). I think the correct VU would be:

> Each of the elements of `pCommandBuffers`, the elements of `pSignalSemaphores`, and the elements of `pWaitSemaphores` of each element of `pSubmits` **must** be created from `VkDevice` parent of `queue`

Locate the implicit same-parent VU for vkQueueSubmit and compare it with the quoted VkSubmitInfo valid-handle requirement. Done means the specification wording requires the handles in pSubmits to use the VkDevice parent of queue, while preserving the stated scope for command buffers, signal semaphores, and wait semaphores.

Written by the indexing model from the issue text.