refactor: prepare to decouple the "model migration" package and "models" package (#38533)

Migrations should never use model structs directly, because the model
structs can be different in different releases. e.g. if one migration uses
"User" model, it works in the early releases, then one day, when the
User model changes, the migration breaks because it will use the
new (incorrect) User model, it should only use the old User model.

The same to "modules/structs".

---------

Signed-off-by: wxiaoguang <wxiaoguang@gmail.com>
Co-authored-by: delvh <dev.lh@web.de>

modelmigration/v1_12/v124.go

@@ -0,0 +1,21 @@
+// Copyright 2020 The Gitea Authors. All rights reserved.
+// SPDX-License-Identifier: MIT
+
+package v1_12
+
+import "gitea.dev/modelmigration/base"
+
+func AddUserRepoMissingColumns(x base.EngineMigration) error {
+	type VisibleType int
+	type User struct {
+		PasswdHashAlgo string      `xorm:"NOT NULL DEFAULT 'pbkdf2'"`
+		Visibility     VisibleType `xorm:"NOT NULL DEFAULT 0"`
+	}
+
+	type Repository struct {
+		IsArchived bool     `xorm:"INDEX"`
+		Topics     []string `xorm:"TEXT JSON"`
+	}
+
+	return x.Sync(new(User), new(Repository))
+}