Move JiHu-specific tables to a dedicated gitlab_main_jh schema

Summary

To improve database organization, maintainability, and clarity between the core GitLab schema and JiHu-specific additions, we propose moving all JiHu-specific tables into a dedicated schema.

Proposal

1. Create a new schema: Introduce a new database schema named gitlab_main_jh.

2. Move JiHu-specific tables: Alter the schema for the following tables to move them from public to gitlab_main_jh.

   Table Name	Justification
   verification_codes	Commented as 'JiHu-specific table'
   content_blocked_states	Commented as 'JiHu-specific table'
   dingtalk_tracker_data	Commented as 'JiHu-specific table'

Further Considerations

There are other tables (application_settings, user_details) that contain specific columns commented as being 'JiHu-specific'. Moving these entire tables is not feasible as they are fundamental to the core application.

A separate, more involved refactoring effort could be considered in the future to extract these JiHu-specific columns into separate extension tables that would reside in the gitlab_main_jh schema. This issue's scope is limited to moving the tables that are entirely specific to JiHu.

Acceptance Criteria

• Definition dictionary of verification_codes, content_blocked_states, and dingtalk_tracker_data are set to be using the gitlab_main_jh schema.
• All existing functionality related to these tables remains fully operational after the change.