[RFC] fix: `_typedExpression` casts boolean to int

Bug or feature?

  it('...', () => {
    const fn = tgpu.fn(() => {
      'use gpu';
      let a = d.u32();
      a = true;
    });

    expect(tgpu.resolve([fn])).toMatchInlineSnapshot(`
      "fn fn_1() {
        var a = 0u;
        a = 1u;
      }"
    `);
  });

This means that booleans are allowed where they shouldn't be:

  it('...', () => {
    const fn = tgpu.fn(() => {
      'use gpu';
      let a = std.sin(true);
    });

    expect(tgpu.resolve([fn])).toMatchInlineSnapshot(`
      "fn fn_1() {
        let a = 0.8414709848078965f;
      }"
    `);
  });

This is a bigger issue when boolean type is allowed by TS and disallowed by WGSL, eg. in switch tests

Start at the _typedExpression implementation and reproduce the two tgpu.fn/tgpu.resolve examples from the issue, then inspect the referenced switch tests. The fix is done when boolean expressions are no longer accepted or emitted as numeric values where the target shader type disallows them.