spirv-val: Add SPV_KHR_ray_tracing storage class

[sjfricke]

Adds validation to make sure all the ray tracing Storage Class are using the correct execution model. Also HitAttributeKHR and ShaderRecordBufferKHR have read/write limitations. There is already validation for the "cannot have initializers" marked as VUID-StandaloneSpirv-OpVariable-04651

(tasklist KhronosGroup/Vulkan-Docs#1402)

[alan-baker]

Are the VUIDs not attachable in RegisterStorageClassConsumer?

[sjfricke]

So right now waiting on KhronosGroup/Vulkan-Docs#1895 to add the VUs, if they decide to keep/add the missing ones I will come back and label them

[alan-baker]

Maybe I'm confused but https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-StandaloneSpirv-IncomingRayPayloadKHR-04699 and other around there seem just like this. Restrictions on the execution models that can use a storage class.

[sjfricke]

I guess my logic was these VUs language (and a few that are missing) are already listed in the SPV_KHR_ray_tracing spec

[sjfricke]

@alan-baker added the VU and when the KhronosGroup/Vulkan-Docs#1895 is merged and upstreamed will add the final 2 labels

[sjfricke]

Had to fix that the Intersection stage can be read from with HitAttribute storage class

Also think I fixed the CI issue with clang-format, not sure what version the CI is using and the utils/clang-format-diff.py script it calls it in the .gitignore and I can't run locally

[sjfricke]

ERROR: /Volumes/BuildData/tmpfs/src/github/SPIRV-Tools/BUILD.bazel:550:10: Compiling test/val/val_decoration_test.cpp failed: (Aborted): wrapped_clang_pp failed: error executing command external/local_config_cc/wrapped_clang_pp '-D_FORTIFY_SOURCE=1' -fstack-protector -fcolor-diagnostics -Wall -Wthread-safety -Wself-assign -fno-omit-frame-pointer -O0 -DDEBUG '-std=c++11' ... (remaining 101 arguments skipped)

yet I didn't touch that file, rebased, hope this finally fixes/pleases CI (cc @alan-baker )