Vulkan: Avoid INT_MAX resource limits
Vulkan: Avoid INT_MAX resource limits

dEQP queries resource limits in all formats, including float.  When
INT_MAX is queried as float, the resulting value is INT_MAX+1 due to
floating point imprecision.  dEQP casts this value back to int for
verification, and trips up on the resulting negative number.

This change limits every ridiculously-large limit to INT_MAX/2 instead
of INT_MAX.

Bug: angleproject:4309
Change-Id: I11018c2c5a0c8bfb410928b0a4c34c526fab2269
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2006813
Commit-Queue: Ian Elliott <ac50c12f27752fd82643b0b72adab33538bb2c97@google.com>
Reviewed-by: Jamie Madill <7e492b4f1c8458024932de3ba475cbf015424c30@chromium.org>
Reviewed-by: Ian Elliott <ac50c12f27752fd82643b0b72adab33538bb2c97@google.com>

ppy/angle,ppy/angle,ppy/angle,ppy/angle