docs: fix migration guide title

[M0NsTeRRR]

Description

docs: fix migration guide title

How Has This Been Tested?

Screenshots / Logs (if applicable)

Checklist:

• I have read and followed the contribution guidelines.
• Disclosed any use of AI (see our policy)
• I have updated the documentation accordingly.
• All new and existing tests passed.
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

Summary by CodeRabbit

• Documentation
  • Reorganized the migration guide's installation method sections for significantly improved navigation and overall readability. The structural updates provide clearer organization of all installation options and associated guidance, making it easier for users to quickly locate and understand all available installation methods. All existing documentation content remains complete and fully accessible.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation restructuring in the migration guide. Reorganized "Third-party installation methods" as a top-level section with "Nix" promoted to a subsection beneath it, while preserving all original content.

Changes

Cohort / File(s)	Summary
Documentation Restructuring docs/migration-guide.mdx	Reorganized heading hierarchy to elevate "Third-party installation methods" to top-level section with "Nix" as child subsection. Content unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 The docs get a facelift so neat and so clean,
Headings rearranged like a well-ordered scene,
Nix finds its home 'neath a parent so grand,
Third-party methods now perfectly planned! ✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: fix migration guide title' accurately reflects the main change: restructuring heading hierarchy in the migration guide documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into develop

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch docs/migration-guide-title

---

No actionable comments were generated in the recent review. 🎉

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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