Skip db dictionary generate in jh

What does this MR do and why?

Since some database tables are specific to JiHu, such as content_blocked_states and verification_codes, these table class models only exist in the JiHu repository. To prevent the db:dictionary:generate task from updating the database documentation's class information, we need to skip it in the JiHu repository.

diff after run db:migrate in JiHu:

diff --git a/db/docs/content_blocked_states.yml b/db/docs/content_blocked_states.yml
index 38349b2014af..0689d4041221 100644
--- a/db/docs/content_blocked_states.yml
+++ b/db/docs/content_blocked_states.yml
@@ -1,6 +1,7 @@
 ---
 table_name: content_blocked_states
-classes: []
+classes:
+- ContentValidation::ContentBlockedState
 feature_categories:
 - source_code_management
 description: JiHu only. Keeps list of restricted blobs.
diff --git a/db/docs/dingtalk_tracker_data.yml b/db/docs/dingtalk_tracker_data.yml
index cd9e8f866028..6994bd805a73 100644
--- a/db/docs/dingtalk_tracker_data.yml
+++ b/db/docs/dingtalk_tracker_data.yml
@@ -1,6 +1,7 @@
 ---
 table_name: dingtalk_tracker_data
-classes: []
+classes:
+- Integrations::DingtalkTrackerData
 feature_categories:
 - integrations
 description: Data related to the Dingtalk integration (JiHu-specific, see https://jihulab.com/gitlab-cn/gitlab/-/merge_requests/417).
diff --git a/db/docs/integrations.yml b/db/docs/integrations.yml
index 5bb4f4485417..6ddb79a6feb0 100644
--- a/db/docs/integrations.yml
+++ b/db/docs/integrations.yml
@@ -19,11 +19,14 @@ classes:
 - Integrations::Confluence
 - Integrations::CustomIssueTracker
 - Integrations::Datadog
+- Integrations::Dingtalk
 - Integrations::Discord
 - Integrations::DroneCi
 - Integrations::EmailsOnPush
 - Integrations::Ewm
 - Integrations::ExternalWiki
+- Integrations::Feishu
+- Integrations::FeishuBot
 - Integrations::Github
 - Integrations::GitlabSlackApplication
 - Integrations::HangoutsChat
@@ -36,6 +39,7 @@ classes:
 - Integrations::MicrosoftTeams
 - Integrations::MockCi
 - Integrations::MockMonitoring
+- Integrations::Ones
 - Integrations::Packagist
 - Integrations::PipelinesEmail
 - Integrations::Pivotaltracker
diff --git a/db/docs/verification_codes.yml b/db/docs/verification_codes.yml
index 9d0e3f53830b..29490be26392 100644
--- a/db/docs/verification_codes.yml
+++ b/db/docs/verification_codes.yml
@@ -1,6 +1,7 @@
 ---
 table_name: verification_codes
-classes: []
+classes:
+- Phone::VerificationCode
 feature_categories:
 - jihu
 description: Used by the JiHu edition for user verification
diff --git a/db/docs/work_item_types.yml b/db/docs/work_item_types.yml
index 37d2c47de252..445ea9df371d 100644
--- a/db/docs/work_item_types.yml
+++ b/db/docs/work_item_types.yml
@@ -1,7 +1,6 @@
 ---
 table_name: work_item_types
 classes:
-- AddWidgetsForWorkItemTypes::WorkItemType
 - WorkItems::Type
 feature_categories:
 - team_planning
diff --git a/db/docs/work_item_widget_definitions.yml b/db/docs/work_item_widget_definitions.yml
index 59cbca149089..073b0c8cc591 100644
--- a/db/docs/work_item_widget_definitions.yml
+++ b/db/docs/work_item_widget_definitions.yml
@@ -1,7 +1,6 @@
 ---
 table_name: work_item_widget_definitions
 classes:
-- AddWidgetsForWorkItemTypes::WidgetDefinition
 - WorkItems::WidgetDefinition
 feature_categories:
 - team_planning

/cc @daveliu

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.