Provide mechanism for configuring submodule aliases

[zeripath]

Sometimes Gitea users would like submodules when displayed on the website to have
a different alias than what is normally inferred by gitea.

This PR provides a mechanism to configure this.

Fix #15178

Signed-off-by: Andrew Thornton art27@cantab.net

[lunny]

Or we could have a configuration on repository setting UI.

[zeripath]

Or we could have a configuration on repository setting UI.

Yes, were would need a common repository settings table:

type Setting struct {
  ID int64
  UserID int64
  RepoID int64
  Key string
  Value string
}

Which could be used to store per user/per repo settings, with Key, RepoID and UserID forming an unique index.

Then we can remove some crap from repo and user, and allow other common settings

[zeripath]

conflicts resolved @6543

[codecov-commenter]

Codecov Report

Merging #15180 (3ab1816) into main (2f725cb) will increase coverage by 0.03%.
The diff coverage is 48.64%.

@@            Coverage Diff             @@
##             main   #15180      +/-   ##
==========================================
+ Coverage   45.44%   45.47%   +0.03%     
==========================================
  Files         710      710              
  Lines       83880    83917      +37     
==========================================
+ Hits        38122    38165      +43     
+ Misses      39618    39612       -6     
  Partials     6140     6140              

Impacted Files	Coverage Δ
modules/setting/git.go	13.33% <8.33%> (-20.00%)	⬇️
modules/git/submodule.go	72.00% <68.00%> (-2.00%)	⬇️
models/repo_mirror.go	58.69% <0.00%> (-10.87%)	⬇️
services/mirror/mirror.go	9.61% <0.00%> (-7.70%)	⬇️
modules/cron/tasks_basic.go	85.43% <0.00%> (-2.92%)	⬇️
modules/log/event.go	59.90% <0.00%> (-1.89%)	⬇️
modules/queue/workerpool.go	53.81% <0.00%> (-1.15%)	⬇️
services/pull/pull.go	41.99% <0.00%> (ø)
routers/api/v1/repo/pull.go	31.08% <0.00%> (+0.53%)	⬆️
models/repo_list.go	77.82% <0.00%> (+0.77%)	⬆️
... and 10 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2f725cb...3ab1816. Read the comment docs.

[zeripath]

conflicts fixed again

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 months. Thank you for your contributions.

[lunny]

Or we could have a configuration on repository setting UI.

Yes, were would need a common repository settings table:

type Setting struct {
  ID int64
  UserID int64
  RepoID int64
  Key string
  Value string
}

Which could be used to store per user/per repo settings, with Key, RepoID and UserID forming an unique index.

Then we can remove some crap from repo and user, and allow other common settings

Let's wait for that PR #22500 merged first.