Make unstruct resolvable and introduce root.unwrap(TgpuVertexLayout)

[reczkok]

• Tests for unstruct resolution
• Tests for TgpuVertexLayout unwrapping
• Update docs
• Check if feasible to type check if every attribute has a location

closes #747

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[reczkok]

• Check if feasible to type check if every attribute has a location

I experimented with this:

export type HasAllPropsWithLocations<T> = T extends TgpuVertexLayout<infer U>
  ? HasAllPropsWithLocations<U>
  : T extends WgslStruct | Unstruct
    ? {
        [K in keyof T['propTypes']]: HasAllPropsWithLocations<
          T['propTypes'][K]
        >;
      }[keyof T['propTypes']] extends false
      ? false
      : true
    : T extends { elementType: unknown }
      ? HasAllPropsWithLocations<T['elementType']>
      : HasCustomLocation<T> extends false
        ? false
        : true;

but keep running into Type instantiation is excessively deep and possibly infinite error

[mhawryluk]

what do we do about [~unstable] in published examples. I'd say we either

1. make vertexLayout stable, docs public and release 0.3.3 right after merging this PR
2. make boids experimental
3. do nothing

[reczkok]

I'm kinda a fan of option 1

[iwoplaza]

Let's do option 1 🚀
I have changed the target to a next branch, which we will accumulate any new features and docs about them until 0.4.0

[mhawryluk]

Great!

[iwoplaza]

This is a really nice addition, awesome!! 🚀

[iwoplaza]

Thank you ChatGPU 🫡

Suggested change

	The above example is great if the vertex buffer will also be used as a storage or uniform buffer. However, if you're only interested in the vertex data, you can use a loose schema instead.
	It is not restricted by alignment rules and can utilize many useful [vertex formats](https://www.w3.org/TR/webgpu/#vertex-formats). To create loose schemas, use `d.unstruct` instead of `d.struct` and `d.disarrayOf` instead of `d.arrayOf`.
	Inside of loose schemas you can use vertex formats as well as the usual data types.
	If the vertex buffer is not required to function as a storage or uniform buffer, a *loose schema* may be used to define the vertex data layout. Loose schemas are not subject to alignment restrictions and allow the use of various [vertex formats](https://www.w3.org/TR/webgpu/#vertex-formats).
	To define a loose schema:
	- Use `d.unstruct` instead of `d.struct`.
	- Use `d.disarrayOf` instead of `d.arrayOf`.
	Within a loose schema, both standard data types and vertex formats can be utilized.

[iwoplaza]

Suggested change

	color: d.unorm8x4, // 4x8-bit unsigned normalized
	// four 8-bit values, unsigned & normalized
	// i.e., four integers in (0, 255) represent four floats in the range of (0.0, 1.0)
	color: d.unorm8x4,

[iwoplaza]

Suggested change

	If you are using a loose schema, you can now resolve it to get its WGSL representation.
	Loose schemas can be interpreted in multiple ways within a shader. However, for convenience, they can be resolved to their default WGSL representation.