feat: Source maps #2935

The goal of this macrotask is to link to an appropriate line and character when 'use gpu' functions turns out to be invalid.

• Add a node wrapper for Identifier, so that it can be sourcemapped (feat: Add Identifier and Bool nodes #2973)
• Create a function for extracting sourcemaps from tinyest (feat: Add source mapping functions #3023)
• Accept source maps in transpileFn (feat: Embed source maps in tinyest-for-wgsl #2975)
• Collect source maps in plugin (feat: Add source mapping option to unplugin #2942)
• Include filename in metadata (feat: Include filename in metadata #3039)
• Include source of error in WGSL errors (feat: Include sourcemap in errors #3282)
• Update wgsl errors to all go through a report function that returns never (so that we can later use eval there)
• Document the feature
• Make the error link clickable
• Try to report source for all items in stack trace
  We could fake-include the errorous file in the stack trace, like WESL does. Something like this:

const fileUrl = `${window.location.origin}/src/main.ts?raw`;

const sourceMap = {
  version: 3,
  file: 'fakeErrorFile.js',
  sources: [fileUrl],
  mappings: `AA${toVLQ(/* line */ 11)}${toVLQ(/* char */ 4)}`,
};

const base64Map = btoa(
  String.fromCharCode(...new TextEncoder().encode(JSON.stringify(sourceMap))),
);

const errFile = `\
throw new Error(':c');
//# sourceMappingURL=data:application/json;base64,${base64Map}
//# sourceURL=apps/typegpu-docs/src/examples/simple/triangle/index.ts
`;
eval(errFile);

(RFC, extra work outside of original scope) Handle device errors.
WESL provides WeslDevice that takes generated source maps into account. We could do the same.
We should probably start with just catching and re-throwing errors. This may allow for easier RN debugging.
This will require us to collect another source map of generated WGSL.