Add matrix overflow test cases.

[dj2]

This CL tests that const-eval of matric operations cause over/under flow.

Fixes: #3682

---

Requirements for PR author:

• [x] All missing test coverage is tracked with "TODO" or .unimplemented().
• [x] New helpers are /** documented */ and new helper files are found in helper_index.txt.
• [x] Test behaves as expected in a WebGPU implementation. (If not passing, explain above.)
• [x] Test have be tested with compatibility mode validation enabled and behave as expected. (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.

[dj2]

Yea, I wasn't sure if it was worth doing more, seemed like if you're const eval-ing one, you'd be doing them all.

[dj2]

I extended the tests to run over all the matrix sizes. I've also added a set of tests where the overflow happens during the internal addition instead of the initial multiplication.