docs(organizeImports): add a note for full import merging

[Conaclos]

Summary

Add a note about full import merging for organizeImports.
This should reduce the number of question we got around this subject.

Test Plan

Nothing to test.

Docs

No changelog needed.

[changeset-bot]

⚠️ No Changeset found

Latest commit: fd22da6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

Documentation has been added to the organise imports assist without any functional code changes. The additions include new examples illustrating how inline-type imports merge with other imports—such as combining type T3 with regular imports like V1 in a single statement. The documentation also includes configuration guidance for the useImportType setting and clarifications about safe fixes.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the primary change: adding documentation about full import merging for the organizeImports feature.
Description check	✅ Passed	The description is directly related to the changeset, explaining the purpose of adding a note about import merging to reduce user confusion.

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

✨ Finishing touches

• 📝 Generate docstrings

---

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

[codspeed-hq]

Merging this PR will not alter performance

✅ 58 untouched benchmarks
⏩ 95 skipped benchmarks¹

---

_{Comparing conaclos/organizeImports-docs (fd22da6) with main (0bf5be1)}

Footnotes

1. 95 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩