chore: remove outdated troubleshooting doc

[LesnyRumcajs]

Summary of changes

Changes introduced in this pull request:

• I don't think anyone used this doc in quite some time so there's no point in migrating it. The link checker also complains there. https://github.com/ChainSafe/forest/actions/runs/18004878245/job/51222639447?pr=6118

Reference issue to close (if applicable)

Closes

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Summary by CodeRabbit

• Documentation
  • Removed the “Troubleshooting” page that covered jemalloc-related issues on Apple Silicon Macs.
  • Updated the documentation navigation to remove the “Troubleshooting” entry from the User Guide.
  • No other documentation sections were modified.

[coderabbitai]

Walkthrough

Removed the Troubleshooting document and its navigation entry from the documentation. Specifically, deleted documentation/src/trouble_shooting.md and removed its link from documentation/src/SUMMARY.md. No code or API/public declarations were changed.

Changes

Cohort / File(s)	Summary of Changes
Docs nav update documentation/src/SUMMARY.md	Removed the Troubleshooting entry from the User Guide section.
Troubleshooting doc removal documentation/src/trouble_shooting.md	Deleted the entire Troubleshooting page covering jemalloc issues on Apple Silicon Macs.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• elmattic
• akaladarshi

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title accurately reflects the removal of the outdated troubleshooting documentation and follows the conventional "chore" prefix to indicate maintenance work. It is concise and clearly communicates the main change to teammates scanning the history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-link-check-1

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a68b350 and 3cb8b5f.

📒 Files selected for processing (2)

• documentation/src/SUMMARY.md (0 hunks)
• documentation/src/trouble_shooting.md (0 hunks)

💤 Files with no reviewable changes (2)

• documentation/src/trouble_shooting.md
• documentation/src/SUMMARY.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: All lint checks
• GitHub Check: Build forest binaries on Linux AMD64
• GitHub Check: cargo-publish-dry-run
• GitHub Check: Build MacOS
• GitHub Check: Build Ubuntu
• GitHub Check: tests-release
• GitHub Check: tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[elmattic]

What should we do with the failed jobs? A wise man once said, 'No green check mark, no reviews', and he kept mumbling it!

[LesnyRumcajs]

What should we do with the failed jobs? A wise man once said, 'No green check mark, no reviews', and he kept mumbling it!

#6117