Contrary claims on whether QFOT can be performed via Events

Similarly to #1516 it is not clear whether Events2 can perform QFOT.

The Queue Family Ownership Transfer chapter says:

> the release and acquire operations of a queue family ownership transfer **can** only be performed using`vkCmdPipelineBarrier`.

But `vkCmdSetEvent2` and `vkCmdWaitEvents2` does seem to have the parameters to do it, and they don't seem restricted by VU (like they are for `vkCmdWaitEvents`.

Additionally, `vkCmdSetEvent2` spec seems to comment on QFOT, though I am not sure it makes any coherent sense:

> Queue family ownership transfers and image layout transitions defined by `pDependencyInfo` are also included in the first scopes.
>
> The second synchronization scope includes only the event signal operation, and any queue family ownership transfers and image layout transitions defined by `pDependencyInfo`.
>
> The second access scope includes only queue family ownership transfers and image layout transitions.

Read issue #1516 and the Queue Family Ownership Transfer chapter alongside the vkCmdSetEvent2 and vkCmdWaitEvents2 specification entries. Determine whether Events2 permits QFOT and resolve the quoted synchronization-scope wording. Done means the relevant specification text and valid-usage language consistently answer the question.

Written by the indexing model from the issue text.