Remove read-to-read barrier warning for barriers with src=VK_ACCESS_TRANSFER_READ_BIT and dst=VK_ACCESS_SHADER_READ_BIT

This warning appears when enabling NVIDIA-side best practices layer.
As far as I know, no other layers ever complain about this.

I can understand that read-to-read barriers do not make sense... **unless** they are performed for different stages in the pipeline. To warn blindly that it is a read-to-read barrier, without analyzing the rest of the data, is not really useful as a validation or performance warning.

Request to remove the warning, or to modify the validation to analyze also the remaining barrier data before issuing a warning.

Start by locating the NVIDIA best-practices warning for barriers with src=VK_ACCESS_TRANSFER_READ_BIT and dst=VK_ACCESS_SHADER_READ_BIT, then inspect how barrier stages and access masks are evaluated. Determine whether the warning should be removed or conditioned on the remaining barrier data. Done means this case no longer produces an unjustified warning while relevant validation remains intact.

Written by the indexing model from the issue text.