v1.9.1升级v1.10.0 migrate失败

Nobody has claimed this yet.

### 重现步骤

1、按升级步骤执行src/init_sql/v1.10.0.sql
2、执行python manage.py migrate 报错
Running migrations:
No migrations to apply.
Your models in app(s): 'sql' have changes that are not yet reflected in a migration, and so won't be applied.
Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.
3、按提示执行python manage.py makemigrations
It is impossible to add a non-nullable field 'id' to config without specifying a default. This is because the database needs something to populate existing rows.
Please select a fix:
1) Provide a one-off default now (will be set on all existing rows with a null value for this column)
2) Quit and manually define a default value in models.py.

### 预期外的结果

数据库合并失败，前台用户无法查询到已授权的数据库实例

### 日志文本

_No response_

### 版本

1.10.0

### 部署方式

Docker

### 是否还有其他可以辅助定位问题的信息？比如数据库版本等

_No response_

Start by reviewing src/init_sql/v1.10.0.sql and reproduce the upgrade with python manage.py migrate, then run python manage.py makemigrations to inspect the reported config.id change. Trace the migration state for the sql app and verify that the upgrade completes without prompting for a default and that authorized database instances become queryable.

Written by the indexing model from the issue text.