Use largest maxInterStageShaderVariables in maxInterStageShaderCompon…

[Jiawei-Shao]

…ents tests

This patch uses the largest value of maxInterStageShaderVariables supported on current adapter in the tests about maxInterStageShaderComponents when creating devices so that when the value we use as maxInterStageShaderComponents is larger than the default one, we won't be limited by the default value of maxInterStageShaderVariables.

This patch also removes the assertion that the value of maxInterStageShaderVariables must be larger than a quarter of maxInterStageShaderComponents as on many backends the largest value of maxInterStageShaderComponents is equal to 4x maxInterStageShaderVaraibles, so in "overLimit" tests the value of maxInterStageShaderComponents can be greater than 4x device.limits.maxInterStageShaderVaraibles.

Issue: #2195

---

Requirements for PR author:

• [*] All missing test coverage is tracked with "TODO" or .unimplemented().
• [*] New helpers are /** documented */ and new helper files are found in helper_index.txt.
• [*] Test behaves as expected in a WebGPU implementation. (If not passing, explain above.)

Requirements for reviewer sign-off:

• Tests are properly located in the test tree.
• Test descriptions allow a reader to "read only the test plans and evaluate coverage completeness", and accurately reflect the test code.
• Tests provide complete coverage (including validation control cases). Missing coverage MUST be covered by TODOs.
• Helpers and types promote readability and maintainability.

When landing this PR, be sure to make any necessary issue status updates.

[github-actions]

Previews, as seen when this build job started (bedab90):
Run tests | View tsdoc

[jiangzhaoming]

Looks good to me, thanks