docs: improve clarity and structure of upgrade process section

[d-bytebase]

Summary

• Reorganized upgrade steps with clear numbered headers for better readability
• Improved professional tone throughout the documentation
• Simplified backup instructions to avoid redundancy and confusion

Changes Made

• Added descriptive step headers (Step 1, Step 2, Step 3) with clear purposes
• Removed duplicate warnings and consolidated backup instructions
• Removed unused import statement and TerminalDockerRunVolume component
• Enhanced formatting with better emphasis on critical information

Test Plan

• Preview the documentation changes locally
• Verify all links still work correctly
• Ensure the upgrade process steps are clear and actionable

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
bytebase-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 11, 2025 9:38am

[Copilot]

Pull Request Overview

Improves documentation clarity and organization by restructuring the upgrade process section with clearer step-by-step instructions and professional tone enhancements.

• Reorganized upgrade steps with descriptive numbered headers for better readability
• Consolidated and improved backup instructions to reduce redundancy
• Removed unused import and component references

[github-actions]

📝 Broken Links Check Report

Note: Entries under /api-reference/ are likely false positives and can be ignored.

The following is the output from the broken links check:

found 16 broken links in 9 files

integrations/api/audit-log.mdx
 ⎿  /api-reference/auditlogservice/post-v1auditlogs:search

integrations/api/authentication.mdx
 ⎿  /api-reference/authservice/post-v1authlogin

integrations/api/data-classification.mdx
 ⎿  /api-reference/settingservice/patch-v1settings
 ⎿  /api-reference/databaseservice/patch-v1instances-databases

integrations/api/issue.mdx
 ⎿  /api-reference/issueservice/post-v1projects-issues

integrations/api/permission.mdx
 ⎿  /api-reference/workspaceservice/get-v1workspaces-:getIamPolicy
 ⎿  /api-reference/projectservice/get-v1projects-:getIamPolicy
 ⎿  /api-reference/roleservice/get-v1roles
 ⎿  /api-reference/userservice/get-v1users
 ⎿  /api-reference/groupservice/get-v1groups

integrations/api/plan.mdx
 ⎿  /api-reference/planservice/post-v1projects-plans
 ⎿  /api-reference/sheetservice/post-v1projects-sheets

integrations/api/release.mdx
 ⎿  /api-reference/releaseservice/post-v1projects-releases

integrations/api/rollout.mdx
 ⎿  /api-reference/rolloutservice/post-v1projects-rollouts

integrations/api/sql-review.mdx
 ⎿  /api-reference/releaseservice/post-v1projects-releases:check
 ⎿  /api-reference/sqlservice/post-v1sqlcheck

[tianzhou]

LGTM