Add documentation for persisting Rust coredumps

[lukevalenta]

Summary

This was written about in the linked blog post. It seems like this should in theory work for Javascript workers, but I'm not sure (e.g., cloudflare/wasm-coredump#5).

Documentation checklist

• The documentation style guide has been adhered to.

[hyperlint-ai]

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.

---

PR Change Summary

Added documentation for persisting Rust coredumps in Workers applications.

• Introduced a section on collecting and persisting Wasm core dumps from Rust Workers applications.
• Provided links to relevant resources including the Wasm Coredump Service and a blog post for further details.

Modified Files

• src/content/docs/workers/observability/errors.mdx

---

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

[lukevalenta]

@celso @xtuc in case you'd like to add more detail to these docs.