Differences between our subgroup implementation and the WebGPU proposal

[teoxoy]

The purpose of this issue is to track the differences between our implementation and the WebGPU proposal so that we can ideally move both in the same direction.

Subgroup support landed in #5301.
The WebGPU proposal landed in gpuweb/gpuweb#4368.

Differences:

• Missing quad operations ([naga] Implement subgroup quad ops #5684).
• Missing subgroupElect.
• Slightly different naming (sum vs add and product vs mul) Adjusts subgroup built-in name verbs to match atomics operations gpuweb/gpuweb#4627.
• Extra barrier feature Add subgroup barrier to subgroups proposal gpuweb/gpuweb#4437.
• Extra add/mul inclusive scan operations with polyfill on HLSL Add inclusive scan add and mul operations gpuweb/gpuweb#4822.
• Extra WGSL builtin attributes num_subgroups and subgroup_id with polyfill on HLSL.
• Extra validation for subgroup_id & subgroup_invocation_id, they are only allowed in compute stages with one dimensional workgroup sizes (since we are not confident that the HLSL polyfill works for workgroup sizes with multiple dimensions; see previous conversation for more info Subgroup Operations #5301 (comment)).

[Lichtso]

The standard changed their naming to match ours, so "Slightly different naming (sum vs add and product vs mul)" can be removed: gpuweb/gpuweb#4627