chore: More strict `std` generator path signatures

it('...', () => {
  // @ts-expect-error
  expect(() => lt(vec3u(), vec3f())).toThrowErrorMatchingInlineSnapshot(
    `[Error: Unsupported signature. Expected the following kinds to be equal: 'vec3u, vec3f'.]`,
  );

  const f = () => {
    'use gpu';
    const x = vec3u();
    // @ts-expect-error
    return lt(x, vec3f());
  };

  expect(tgpu.resolve([f])).toMatchInlineSnapshot(`
    "fn f() -> vec3<bool> {
      let x = vec3u();
      return (x < vec3f());
    }"
  `);
});

Locate the test containing the shown lt, vec3u, and vec3f calls, then trace the std generator path handling used by that test. Run the test and confirm mismatched vector kinds produce the expected TypeScript error and runtime message while the generated fn f() snapshot remains as shown.