chore: remove changelist feature references (#926)

Remove references to the deprecated changelist feature from blog posts,
documentation images, and pricing plans to reflect current product offering.

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

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

Author: boojack

content/blog/cvte-case-study.md

@@ -54,7 +54,6 @@ Besides emphasizing control throughout the release process, Bytebase provides va
 
 - **Batch changes**: Bytebase supports multiple ways to release changes, among which [Batch Change](https://docs.bytebase.com/change-database/batch-change/) can group and release changes to a large number of databases simultaneously, avoiding database-by-database execution, and can flexibly handle cross-grouping issues, which simply cannot be addressed by customizing batch change scripts.
 - **Script validation**: Bytebase helps write better SQL statements by incorporating syntax checking and object name verification. For certain operations, such as modifying schema referenced by VIEWs (in PostgreSQL, the VIEW needs to be deleted to modify table schema), Bytebase can automatically provide VIEW definitions for easy script rewriting.
-- **Simplified version control**: Before Bytebase, change scripts in test environments needed to be manually recorded and arranged using tools like spreadsheets, before being individually released into production environments. This process was cumbersome and prone to errors. With [Changelist](https://docs.bytebase.com/changelist/), they can now import changes from change history or external files and release them with one click, significantly improving the experience.
 
 ### Integrating Compliance
 

content/blog/database-version-control.md

@@ -36,12 +36,6 @@ Version control systems store the history of changes made to the database schema
 
 ![change-history-diff](/content/blog/database-version-control/change-history-diff.webp)
 
-## Migration Scripts
-
-Database version control often relies on migration scripts, which are code files that define the necessary changes to the database schema. These scripts typically contain SQL statements or other database-specific commands to create, modify, or delete database objects. In Bytebase, one can use [Changelist](https://docs.bytebase.com/changelist/) to compose the migration scripts.
-
-![change-list](/content/blog/database-version-control/changelist.webp)
-
 ## Deployment and Rollback
 
 By keeping a history of changes, version control enables controlled deployment of database updates. If a problem occurs, it allows teams to roll back to a previous version of the database schema and associated data. Bytebase provides the following rollback options:

content/blog/use-jira-for-database-change.md

@@ -66,7 +66,7 @@ It's challenging to force a general issue ticketing system to handle the special
 ## Why Bytebase
 
 Many customers come to [Bytebase](/) from Jira because of the aforementioned challenges. Similar to Jira,
-Bytebase has the concepts of `Project`, `Issue`. Additionally, Bytebase defines some database domain-specific concepts as first-class citizens, such as `Database Instance`, `Database`, `Environment`, `Changelist`. Bytebase provides an integrated
+Bytebase has the concepts of `Project`, `Issue`. Additionally, Bytebase defines some database domain-specific concepts as first-class citizens, such as `Database Instance`, `Database`, `Environment`. Bytebase provides an integrated
 experience to plan, review, and deploy database changes.
 
 ![Issue detail interface](/content/blog/use-jira-for-database-change/issue-detail.webp)