`spirv-std` features for APIs that are not universally available

OTOH, there does exist a SequentiallyConsistent in SPIR-V, so if we wanted to, we could move the error to the new SPIR-T-based validator pass, so you're only going to see if the match ordering {...} doesn't get optimized away.

Originally posted by @eddyb in #399

This is another frustrating part of rust-gpu for me. It exposes all possible permutations of things possible in SPIR-V, even though some of them are only possible in a specific version, some only in OpenCL (is it even a relevant target at this point?), and some are technically valid for Vulkan as such, but not supported by WebGPU/wgpu.

It'd be nice if spirv-std had features flags that hide certain APIs that are specific to Vulkan-only or OpenCL-only or require a specific SPIR-V version (ideally, with Vulkan version aliases).

Some meta feature that only exposes portable features usable with wgpu would be useful as well, but that might be a stretch (though it would be a serious usability improvement).

Comienza revisando la superficie de la API de spirv-std y la discusión referenciada sobre los validadores de SPIR-V y SPIR-T. Define qué APIs deberían estar condicionadas por los requisitos de portabilidad de Vulkan, OpenCL, SPIR-V o wgpu, y considera cómo se representarían los alias de features; se considera completado cuando los límites de las features y el comportamiento de portabilidad están especificados e implementados.