docs: remove deployment config and multi tenancy

Author: tianzhou

content/changelog/bytebase-3-5-0.md

@@ -12,21 +12,22 @@ description: 'Azure IAM Auth for Cosmos DB & Azure SQL'
 
 ## 🔔 Breaking Changes
 
-- Deprecated [slow query feature](https://www.bytebase.com/docs/slow-query).
-- To simplify the deployment process, the [custom deployment configuration feature](https://www.bytebase.com/docs/change-database/batch-change/#deployment-config) has been removed. Deployments will now follow the straightforward order of your defined environments. For canary deployments, create a separate `canary` environment. Then, point your database environment to this canary environment.
-- Deprecated [multitenancy feature](https://www.bytebase.com/docs/change-database/batch-change/#multitenancy).
+- Deprecated slow query feature.
+- To simplify the deployment process, the custom deployment configuration feature has been removed. Deployments will now follow the straightforward order of your defined environments. For canary deployments, create a separate `canary` environment. Then, point your database environment to this canary environment.
+- Deprecated multitenancy feature.
 - Deprecated [built-in GitOps feature](https://www.bytebase.com/docs/vcs-integration/overview/#legacy-gitops), now you can use [GitOps in a new way](https://www.bytebase.com/docs/tutorials/gitops-github-workflow/).
 - API support pagination and filter.
+
   - ListProjects support `page_size` and `page_token`. [Doc](https://api.bytebase.com/#tag/projectservice/GET/v1/projects)
   - SearchProjects support filter by `name` and `resource_id`. [Doc](https://api.bytebase.com/#tag/projectservice/POST/v1/projects:search)
   - ListDatabases support filter by `environment/project/instance/name/engine/label/exclude_unassigned`. [Doc](https://api.bytebase.com/#tag/databaseservice/GET/v1/instances/{instance}/databases)
   - ListUsers support filter by `name/email/user_type/state`. [Doc](https://api.bytebase.com/#tag/userservice/GET/v1/users)
 
   These API changes bring huge UI change and influence many features:
 
-    - Will NOT list all projects anymore, users must fetch projects per page, or search projects by name/resource id. (For the project table & selector)
-    - Will NOT list all databases anymore, users must fetch databases per page, or search databases by filter. (Almost all features are affected as long as it's using the database, for example, issue, release, rollout, database group, masking, SQL editor)
-    - Will NOT list all users anymore, users must fetch users per page, or search users by name/email. (Many features are affected as long as it's using the user, for example, issue, release, group, member/IAM)
+  - Will NOT list all projects anymore, users must fetch projects per page, or search projects by name/resource id. (For the project table & selector)
+  - Will NOT list all databases anymore, users must fetch databases per page, or search databases by filter. (Almost all features are affected as long as it's using the database, for example, issue, release, rollout, database group, masking, SQL editor)
+  - Will NOT list all users anymore, users must fetch users per page, or search users by name/email. (Many features are affected as long as it's using the user, for example, issue, release, group, member/IAM)
 
 ## 🚀 New Features
 

content/docs/change-database/batch-change.md

@@ -33,7 +33,7 @@ If you always change a fixed set of databases together, you can pre-define a `da
 
    ![bb-project-groups-create](/content/docs/change-database/batch-change/bb-project-groups-create.webp)
 
-1. Fill in the name and rules for filtering the desired databases. You can enable [Multitenancy](#multitenancy) to enforce extra schema consistency.
+1. Fill in the name and rules for filtering the desired databases.
 
    ![bb-new-db-group-with-raw](/content/docs/change-database/batch-change/bb-new-db-group-with-raw.webp)
 
@@ -55,58 +55,3 @@ If you always change a fixed set of databases together, you can pre-define a `da
 1. An issue with the selected databases will be previewed. Add the SQL in the text field and click **Create**. The issue is created and waiting for approval.
 
    ![bb-issue-batch-created](/content/docs/change-database/batch-change/bb-issue-batch-created.webp)
-
-### Multitenancy
-
-<HintBlock type="warning">
-
-This feature is deprecated since 3.5.0.
-
-</HintBlock>
-
-<HintBlock type="info">
-
-Only applicable if the new database is created via Bytebase.
-
-</HintBlock>
-
-If the database group enables `Multitenancy`, Bytebase will enforce extra schema consistencies:
-
-- If a new database is added to the database group, the new database will be applied with the schema from the first database in the database group.
-
-- Further, if the new database is created via Bytebase when there is an ongoing change to the database group. The new database will be added to the change issue automatically.
-
-  The example below shows we are adding `hr_prod_7` to the existing `hr_prod` database group. And there is an ongoing change
-  to the `hr_prod` group.
-
-  ![bb-db-7](/content/docs/change-database/batch-change/bb-db-add-7.webp)
-
-  Bytebase appends `hr_prod_7` to the change as well.
-
-  ![bb-issue-add-7](/content/docs/change-database/batch-change/bb-issue-add-7.webp)
-
-## Deployment Config
-
-<HintBlock type="warning">
-
-This feature is deprecated since 3.5.0.
-
-</HintBlock>
-
-`Deployment Config` determines how databases or database groups are deployed in order.
-
-![deployment-config](/content/docs/change-database/batch-change/deployment-config.webp)
-
-The above screenshot defines a 3 staged rollout:
-
-1. 1st stage roll outs the prod databases from Asia.
-1. 2nd stage roll outs the prod databases from Europe.
-1. 3rd stage roll outs the prod databases from North America.
-
-![staged-rollout](/content/docs/change-database/batch-change/staged-rollout.webp)
-
-If **all changed databases** are included by the deployment config, Bytebase will roll out them in order
-according to the defined deployment config.
-
-If only some of the changed databases are included by the deployment config, Bytebase will not follow the deployment config.
-Instead Bytebase will roll out them according to their corresponding environments.