fix(wasm): document support and adoption of build_id section (#14597)

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR

This is a follow-up to
#14591.

The current state of the docs (across platforms) does not reflect:

* that the`build_id` section is officially part of the [WASM tooling
conventions](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md)
* that this section is adopted by tooling other than Sentry (in
particular, `LLVM` and thus `emscripten` supports it [since version
17](llvm/llvm-project@c7af9ae))
* how `wasm-split` still fits in this landscape

This PR tries to rectify this.

Open topics:

* It is obvious that `file-formats` and `identifiers` are duplicates
across all platforms with `WASM` support. Of course, these could be
extracted into includes, but I am no longer sure what the current
approach in docs is regarding deduplication of sections.
* I am not sure if the statement regarding WASM source maps (the text
above my changes in the `file-formats` section) still holds, but we can
fix those in another PR.

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [x] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [x] Checked Vercel preview for correctness, including links
- [x] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [x] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## LEGAL BOILERPLATE

<!-- Sentry employees and contractors can delete or ignore this section.
-->

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

---------

Co-authored-by: JoshuaMoelans <[email protected]>

Author: supervacuus

docs/platforms/android/data-management/debug-files/file-formats/index.mdx

@@ -173,8 +173,11 @@ Note that we do not support source maps, which are also a format used for WASM
 debugging, but have shortcomings that make them impractical for a crash reporting
 tool like Sentry.
 
-Since WASM does not specify debug/build IDs yet, we provide a separate tool to
-add build IDs and split files called [wasm-split](https://github.com/getsentry/symbolicator/blob/master/crates/wasm-split)
+[WebAssembly supports build IDs](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md) as a
+[custom section](https://webassembly.github.io/spec/core/binary/modules.html#custom-section). This section
+is a supported by `LLVM` [since version 17](https://github.com/llvm/llvm-project/commit/c7af9ae577bb04c5fe120fc07844a500818c8f47) (and with it, the corresponding `emscripten` toolchain).
+
+In addition to that, we provide a tool to add build IDs and split files called [wasm-split](https://github.com/getsentry/symbolicator/blob/master/crates/wasm-split)
 to help you create a debug companion file ready for uploading to Sentry
 while removing all debug information from the release binary.
 

docs/platforms/android/data-management/debug-files/identifiers/index.mdx

@@ -82,14 +82,14 @@ for symbolication.
 
 ## WASM Build IDs
 
-WebAssembly does not yet support build IDs. The option proposed to
-implement build IDs for WebAssembly ([Build ID Section for WASM](https://github.com/WebAssembly/tool-conventions/issues/133))
-has not yet found widespread adoption. Instead, we use a custom
-extension to WebAssembly.
-
-Our recommendation is to embed a UUID in the `build_id` custom section as
-raw binary. Our [`wasm-split`](https://github.com/getsentry/symbolicator/tree/master/crates/wasm-split)
-tool can do this for you automatically.
+[WebAssembly supports build IDs](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md) as a
+[custom section](https://webassembly.github.io/spec/core/binary/modules.html#custom-section).
+
+`LLVM` (and with it, the corresponding `emscripten` toolchain) supports this [since version 17](https://github.com/llvm/llvm-project/commit/c7af9ae577bb04c5fe120fc07844a500818c8f47).
+
+Our [`wasm-split`](https://github.com/getsentry/symbolicator/tree/master/crates/wasm-split)
+tool can also be used to add a build ID if your toolchain doesn't support this yet. It also allows you
+to split and extract debug information from your `*.wasm` file.
 
 ## ProGuard UUIDs
 

docs/platforms/apple/common/data-management/debug-files/file-formats/index.mdx

@@ -173,8 +173,11 @@ Note that we do not support source maps, which are also a format used for WASM
 debugging, but have shortcomings that make them impractical for a crash reporting
 tool like Sentry.
 
-Since WASM does not specify debug/build IDs yet, we provide a separate tool to
-add build IDs and split files called [wasm-split](https://github.com/getsentry/symbolicator/blob/master/crates/wasm-split)
+[WebAssembly supports build IDs](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md) as a
+[custom section](https://webassembly.github.io/spec/core/binary/modules.html#custom-section). This section
+is a supported by `LLVM` [since version 17](https://github.com/llvm/llvm-project/commit/c7af9ae577bb04c5fe120fc07844a500818c8f47) (and with it, the corresponding `emscripten` toolchain).
+
+In addition to that, we provide a tool to add build IDs and split files called [wasm-split](https://github.com/getsentry/symbolicator/blob/master/crates/wasm-split)
 to help you create a debug companion file ready for uploading to Sentry
 while removing all debug information from the release binary.
 

docs/platforms/apple/common/data-management/debug-files/identifiers/index.mdx

@@ -82,14 +82,14 @@ for symbolication.
 
 ## WASM Build IDs
 
-WebAssembly does not yet support build IDs. The option proposed to
-implement build IDs for WebAssembly ([Build ID Section for WASM](https://github.com/WebAssembly/tool-conventions/issues/133))
-has not yet found widespread adoption. Instead, we use a custom
-extension to WebAssembly.
-
-Our recommendation is to embed a UUID in the `build_id` custom section as
-raw binary. Our [`wasm-split`](https://github.com/getsentry/symbolicator/tree/master/crates/wasm-split)
-tool can do this for you automatically.
+[WebAssembly supports build IDs](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md) as a
+[custom section](https://webassembly.github.io/spec/core/binary/modules.html#custom-section).
+
+`LLVM` (and with it, the corresponding `emscripten` toolchain) supports this [since version 17](https://github.com/llvm/llvm-project/commit/c7af9ae577bb04c5fe120fc07844a500818c8f47).
+
+Our [`wasm-split`](https://github.com/getsentry/symbolicator/tree/master/crates/wasm-split)
+tool can also be used to add a build ID if your toolchain doesn't support this yet. It also allows you
+to split and extract debug information from your `*.wasm` file.
 
 ## ProGuard UUIDs
 

docs/platforms/dart/guides/flutter/data-management/debug-files/file-formats/index.mdx

@@ -173,8 +173,11 @@ Note that we do not support source maps, which are also a format used for WASM
 debugging, but have shortcomings that make them impractical for a crash reporting
 tool like Sentry.
 
-Since WASM does not specify debug/build IDs yet, we provide a separate tool to
-add build IDs and split files called [wasm-split](https://github.com/getsentry/symbolicator/blob/master/crates/wasm-split)
+[WebAssembly supports build IDs](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md) as a
+[custom section](https://webassembly.github.io/spec/core/binary/modules.html#custom-section). This section
+is a supported by `LLVM` [since version 17](https://github.com/llvm/llvm-project/commit/c7af9ae577bb04c5fe120fc07844a500818c8f47) (and with it, the corresponding `emscripten` toolchain).
+
+In addition to that, we provide a tool to add build IDs and split files called [wasm-split](https://github.com/getsentry/symbolicator/blob/master/crates/wasm-split)
 to help you create a debug companion file ready for uploading to Sentry
 while removing all debug information from the release binary.
 

docs/platforms/dart/guides/flutter/data-management/debug-files/identifiers/index.mdx

@@ -82,14 +82,14 @@ for symbolication.
 
 ## WASM Build IDs
 
-WebAssembly does not yet support build IDs. The option proposed to
-implement build IDs for WebAssembly ([Build ID Section for WASM](https://github.com/WebAssembly/tool-conventions/issues/133))
-has not yet found widespread adoption. Instead, we use a custom
-extension to WebAssembly.
-
-Our recommendation is to embed a UUID in the `build_id` custom section as
-raw binary. Our [`wasm-split`](https://github.com/getsentry/symbolicator/tree/master/crates/wasm-split)
-tool can do this for you automatically.
+[WebAssembly supports build IDs](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md) as a
+[custom section](https://webassembly.github.io/spec/core/binary/modules.html#custom-section).
+
+`LLVM` (and with it, the corresponding `emscripten` toolchain) supports this [since version 17](https://github.com/llvm/llvm-project/commit/c7af9ae577bb04c5fe120fc07844a500818c8f47).
+
+Our [`wasm-split`](https://github.com/getsentry/symbolicator/tree/master/crates/wasm-split)
+tool can also be used to add a build ID if your toolchain doesn't support this yet. It also allows you
+to split and extract debug information from your `*.wasm` file.
 
 ## ProGuard UUIDs
 

docs/platforms/dotnet/common/data-management/debug-files/file-formats/index.mdx

@@ -173,8 +173,11 @@ Note that we do not support source maps, which are also a format used for WASM
 debugging, but have shortcomings that make them impractical for a crash reporting
 tool like Sentry.
 
-Since WASM does not specify debug/build IDs yet, we provide a separate tool to
-add build IDs and split files called [wasm-split](https://github.com/getsentry/symbolicator/blob/master/crates/wasm-split)
+[WebAssembly supports build IDs](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md) as a
+[custom section](https://webassembly.github.io/spec/core/binary/modules.html#custom-section). This section
+is a supported by `LLVM` [since version 17](https://github.com/llvm/llvm-project/commit/c7af9ae577bb04c5fe120fc07844a500818c8f47) (and with it, the corresponding `emscripten` toolchain).
+
+In addition to that, we provide a tool to add build IDs and split files called [wasm-split](https://github.com/getsentry/symbolicator/blob/master/crates/wasm-split)
 to help you create a debug companion file ready for uploading to Sentry
 while removing all debug information from the release binary.
 

docs/platforms/dotnet/common/data-management/debug-files/identifiers/index.mdx

@@ -82,14 +82,14 @@ for symbolication.
 
 ## WASM Build IDs
 
-WebAssembly does not yet support build IDs. The option proposed to
-implement build IDs for WebAssembly ([Build ID Section for WASM](https://github.com/WebAssembly/tool-conventions/issues/133))
-has not yet found widespread adoption. Instead, we use a custom
-extension to WebAssembly.
-
-Our recommendation is to embed a UUID in the `build_id` custom section as
-raw binary. Our [`wasm-split`](https://github.com/getsentry/symbolicator/tree/master/crates/wasm-split)
-tool can do this for you automatically.
+[WebAssembly supports build IDs](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md) as a
+[custom section](https://webassembly.github.io/spec/core/binary/modules.html#custom-section).
+
+`LLVM` (and with it, the corresponding `emscripten` toolchain) supports this [since version 17](https://github.com/llvm/llvm-project/commit/c7af9ae577bb04c5fe120fc07844a500818c8f47).
+
+Our [`wasm-split`](https://github.com/getsentry/symbolicator/tree/master/crates/wasm-split)
+tool can also be used to add a build ID if your toolchain doesn't support this yet. It also allows you
+to split and extract debug information from your `*.wasm` file.
 
 ## ProGuard UUIDs
 

docs/platforms/javascript/common/data-management/debug-files/file-formats/index.mdx

@@ -176,8 +176,11 @@ Note that we do not support source maps, which are also a format used for WASM
 debugging, but have shortcomings that make them impractical for a crash reporting
 tool like Sentry.
 
-Since WASM does not specify debug/build IDs yet, we provide a separate tool to
-add build IDs and split files called [wasm-split](https://github.com/getsentry/symbolicator/blob/master/crates/wasm-split)
+[WebAssembly supports build IDs](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md) as a
+[custom section](https://webassembly.github.io/spec/core/binary/modules.html#custom-section). This section
+is a supported by `LLVM` [since version 17](https://github.com/llvm/llvm-project/commit/c7af9ae577bb04c5fe120fc07844a500818c8f47) (and with it, the corresponding `emscripten` toolchain).
+
+In addition to that, we provide a tool to add build IDs and split files called [wasm-split](https://github.com/getsentry/symbolicator/blob/master/crates/wasm-split)
 to help you create a debug companion file ready for uploading to Sentry
 while removing all debug information from the release binary.
 

docs/platforms/javascript/common/data-management/debug-files/identifiers/index.mdx

@@ -85,14 +85,14 @@ for symbolication.
 
 ## WASM Build IDs
 
-WebAssembly does not yet support build IDs. The option proposed to
-implement build IDs for WebAssembly ([Build ID Section for WASM](https://github.com/WebAssembly/tool-conventions/issues/133))
-has not yet found widespread adoption. Instead, we use a custom
-extension to WebAssembly.
-
-Our recommendation is to embed a UUID in the `build_id` custom section as
-raw binary. Our [`wasm-split`](https://github.com/getsentry/symbolicator/tree/master/crates/wasm-split)
-tool can do this for you automatically.
+[WebAssembly supports build IDs](https://github.com/WebAssembly/tool-conventions/blob/main/BuildId.md) as a
+[custom section](https://webassembly.github.io/spec/core/binary/modules.html#custom-section).
+
+`LLVM` (and with it, the corresponding `emscripten` toolchain) supports this [since version 17](https://github.com/llvm/llvm-project/commit/c7af9ae577bb04c5fe120fc07844a500818c8f47).
+
+Our [`wasm-split`](https://github.com/getsentry/symbolicator/tree/master/crates/wasm-split)
+tool can also be used to add a build ID if your toolchain doesn't support this yet. It also allows you
+to split and extract debug information from your `*.wasm` file.
 
 ## ProGuard UUIDs