docs: reorganize Features tab into Database CI/CD and SQL Editor (#852)

- Split Features tab into two separate tabs for better organization
- Database CI/CD tab contains schema migration and change management features
- SQL Editor tab includes SQL editor, database permissions, and data masking
- Add cross-references from what-is-bytebase page to respective sections

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-authored-by: Claude <[email protected]>

Author: d-bytebase

mintlify/docs.json

@@ -78,7 +78,7 @@
         ]
       },
       {
-        "tab": "Features",
+        "tab": "Database CI/CD",
         "groups": [
           {
             "group": "Database CI/CD",
@@ -148,7 +148,12 @@
               },
               "change-database/troubleshoot"
             ]
-          },
+          }
+        ]
+      },
+      {
+        "tab": "SQL Editor",
+        "groups": [
           {
             "group": "SQL Editor",
             "pages": [

mintlify/introduction/what-is-bytebase.mdx

@@ -12,7 +12,7 @@ It's a unified platform specifically built for your **developer, security, DBA,
 
 ## 🚀 Managing Schema Changes at Scale
 
-This section covers how Bytebase makes all database changes safer and more efficient. By providing a structured process, it also enhances security by **eliminating the need for engineers to make direct changes against databases**. Bytebase supports two distinct workflows for schema changes:
+This section covers how Bytebase makes all database changes safer and more efficient. By providing a structured process, it also enhances security by **eliminating the need for engineers to make direct changes against databases**. Learn more in the [Database CI/CD](/change-database/change-workflow) section. Bytebase supports two distinct workflows for schema changes:
 
 **UI-driven Workflow**: Provides a complete, console-based process with built-in risk analysis and multi-step approvals, offering a secure and self-contained way to manage schema changes.
 
@@ -26,7 +26,7 @@ In addition to these workflows, the platform provides overarching capabilities f
 
 ## 🛡️ Governing Data Access at Scale
 
-This workflow governs how your database data is accessed, replacing the need for disparate SQL clients and shared credentials.
+This workflow governs how your database data is accessed, replacing the need for disparate SQL clients and shared credentials. Explore the full capabilities in the [SQL Editor](/sql-editor/overview) section.
 
 **Centralized Access Control:** Grant data query permissions based on role, not on sharing database passwords. This provides a single place to manage who can see what across your entire environment.