Update location/component conflict validation

[alan-baker]

Refs #5989

• Update input/output interface validation to treat arrays and matrices as consuming all 4 components in each location

This handles the removal of interleaving components among array/matrix elements.

[alan-baker]

I expect this will break some glslang tests because this is allowed (and tested) in glslang.

[spencer-lunarg]

According to the Vulkan Guide article the following GLSL is banned

layout(location=0, component = 1) in float a[3];

because array must not have a component decoration (with the stage exceptions inVUID-StandaloneSpirv-Execution-10584/ VUID-StandaloneSpirv-Execution-10585)

so checking, this change doesn't throw an error for

           OpCapability Shader
           OpMemoryModel Logical GLSL450
           OpEntryPoint Vertex %main "main" %x
           OpDecorate %x Location 0
           OpDecorate %x Component 1
   %void = OpTypeVoid
      %4 = OpTypeFunction %void
   %uint = OpTypeInt 32 0
 %uint_2 = OpConstant %uint 2
%t_array = OpTypeArray %uint %uint_2
    %ptr = OpTypePointer Input %t_array
      %x = OpVariable %ptr Input
   %main = OpFunction %void None %4
      %6 = OpLabel
           OpReturn
           OpFunctionEnd

[alan-baker]

Those VUs say no arrays of arrays. That example is a single level of array. I think there might be missing VUs to ban that example. I had raised vulkan internal issue 4180 for it.