[Doc] Seatunnel Doc Structure Adjustment

[misi1987107]

Purpose of this pull request

related (#10262)
document structure adjustment

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If necessary, please update incompatible-changes.md to describe the incompatibility caused by this PR.
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config

[davidzollo]

Great job.
I suggest deleting docs/en/connectors/overview.md and the Chinese document. Maintaining this doc will be difficult.

[misi1987107]

Great job. I suggest deleting docs/en/connectors/overview.md and the Chinese document. Maintaining this doc will be difficult.

ok,got it

[DanielCarter-stack]

• docs/ (directory structure): Breaking URL change from connector-v2 to connectors will break all existing external links (blogs, tutorials, Stack Overflow answers) without a migration plan. Consider adding 301 redirects or a migration guide to preserve SEO and user bookmarks.

• docs/en/connectors/overview.md (deleted file): The entire 433-line overview file was removed without indicating where the content migrated. If the connector capability matrix was deleted without replacement, users will lose important context about SeaTunnel's connector ecosystem.

• docs/sidebars.js: Navigation config changed from autogenerated to explicit paths (135 lines changed). Without a before/after comparison, some documentation pages may become orphaned and inaccessible via the sidebar.

• docs/zh/: Large-scale updates to both English and Chinese docs lack verification that Chinese content accurately reflects English changes. Inconsistent translations could mislead Chinese-speaking users.

• docs/ (internal links): After restructuring directories (connector-v2 → connectors, moving common-options), internal relative links may be broken. Running a link checker before merge would prevent 404 errors within the documentation.

[zhangshenghang]

LGTM

[davidzollo]

+1
good job