docs: consolidate error code documentation into SQL Review section (#875)

* docs: consolidate error code documentation into SQL Review section

Moved all error code references from /reference/error-code to /sql-review/error-codes.mdx
for better organization and discoverability. This consolidates advisor and core error
codes into a single location within the SQL Review documentation where they are most
relevant to users.

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

Co-Authored-By: Claude <[email protected]>

* docs: add redirects for old error code pages

Added redirects from the old error code documentation paths to the new
consolidated location at /sql-review/error-codes to ensure existing
links and bookmarks continue to work.

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

Co-Authored-By: Claude <[email protected]>

---------

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

Author: d-bytebase

mintlify/changelog/bytebase-0-7-0.mdx

@@ -35,7 +35,7 @@ We currently detect following anomalies and will add more in the future:
 
 ### Backward compatible schema migration check (MySQL/TiDB)
 
-In the last release, we introduce the task check system and introduced the basic SQL syntax check. In this release, we advance the check to catch backward incompatible schema migration (e.g. RENAME TABLE). Introducing backward incompatible schema changes is one of the most common mistakes made by developers and enforcing backward compatible schema change is the standard practice adopted by many engineering organizations. Bytebase now automatically checks all common incompatible schema change [scenarios](https://www.bytebase.com/docs/reference/error-code/advisor/#compatibility) and surface them in the SQL review panel:
+In the last release, we introduce the task check system and introduced the basic SQL syntax check. In this release, we advance the check to catch backward incompatible schema migration (e.g. RENAME TABLE). Introducing backward incompatible schema changes is one of the most common mistakes made by developers and enforcing backward compatible schema change is the standard practice adopted by many engineering organizations. Bytebase now automatically checks all common incompatible schema change [scenarios](https://www.bytebase.com/docs/sql-review/error-codes/#compatibility) and surface them in the SQL review panel:
 ![_](/content/changelog/0.7.0/backward-compatible-check.webp)
 
 ### Backup schedule enforcement

mintlify/docs.json

@@ -135,7 +135,8 @@
           {
             "group": "Appendix",
             "pages": [
-              "sql-review/review-rules"
+              "sql-review/review-rules",
+              "sql-review/error-codes"
             ]
           }
         ]
@@ -225,13 +226,6 @@
               "administration/announcement",
               "administration/archive"
             ]
-          },
-          {
-            "group": "Reference",
-            "pages": [
-              "reference/error-code/core",
-              "reference/error-code/advisor"
-            ]
           }
         ]
       },
@@ -491,6 +485,14 @@
     }
   },
   "redirects": [
+    {
+      "source": "/reference/error-code/advisor",
+      "destination": "/sql-review/error-codes"
+    },
+    {
+      "source": "/reference/error-code/core",
+      "destination": "/sql-review/error-codes"
+    },
     {
       "source": "/get-started/instance",
       "destination": "/get-started/connect/overview"

mintlify/reference/error-code/core.mdx

@@ -1,5 +1,5 @@
 ---
-title: Error Code for SQL Review
+title: Error Codes
 ---
 
 ## General

mintlify/reference/error-code/advisor.mdx mintlify/sql-review/error-codes.mdxmintlify/reference/error-code/advisor.mdx renamed to mintlify/sql-review/error-codes.mdx

@@ -861,7 +861,7 @@ Specifically, Bytebase checks:
 <div id="schema.backward-compatibility"></div>
 ### Backward incompatible schema change
 
-Introducing backward incompatible schema changes is one of the most common mistakes made by developers. And enforcing backward compatible schema change is the standard practice adopted by many engineering organizations. Bytebase provides the built-in backward compatible check to catch all common incompatible schema change [scenarios](https://www.bytebase.com/docs/reference/error-code/advisor/#compatibility).
+Introducing backward incompatible schema changes is one of the most common mistakes made by developers. And enforcing backward compatible schema change is the standard practice adopted by many engineering organizations. Bytebase provides the built-in backward compatible check to catch all common incompatible schema change [scenarios](https://www.bytebase.com/docs/sql-review/error-codes/#compatibility).
 
 ![schema-review-schema-backward-compatibility](/content/docs/sql-review/schema-review-schema-backward-compatibility.webp)