[util] Enable constant buffer range check for NieR:Automata

[Bownairo]

This fixes a graphical corruption issue where Operator 6O's portrait
displays as a large flashing circle due to uninitialized buffer reads.

Fixes issue: ValveSoftware/Proton#1543

Reviewed-by: Liam Middlebrook lmiddlebrook@nvidia.com

[doitsujin]

Is this another case of a shader reading constant buffer data outside of the bound buffer range, but still inside the buffer itself?

I'm willing to accept this as a workaround for now if it doesn't regress anything (this workaround doesn't match D3D11 behaviour), but I feel like we're going to need a real solution eventually, i.e. some way to specify that out-of-bound-range reads return 0 rather than undefined values.

AMD hardware does that anyway, Nvidia doesn't, and both are correct according to the Vulkan spec since robustBufferAccess allows either behaviour.