Add owner_name column for table repository for maintaince reason

[lunny]

As title. Inspired by @zeripath 's comment.

[guillep2k]

This should improve the speed quite a bit.

Just a nit (and the CI that's acting up).

[zeripath]

I don't see any code changing the owner name during transfer repository - have you covered this case?

---

I see it now

[zeripath]

You need to update the test fixtures

[zeripath]

In particular this file:

https://github.com/go-gitea/gitea/blob/master/models/fixtures/repository.yml

Or rather this one:

https://github.com/lunny/gitea/blob/lunny/save_owner_name_repo/models/fixtures/repository.yml

---

Done

[zeripath]

Ok so it looks like there are a few places where owner is expected to be present because it would have been loaded in order to get the owner name. I'm not sure what's best here, it might be that it's easiest to just stick LoadOwner s before every call to repo. Owner but that could easily cause some deadlocks - and that still doesn't necessarily catch the templates.

There's also an issue with a unit test.

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@7b62e9a). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #9717   +/-   ##
=========================================
  Coverage          ?   42.23%           
=========================================
  Files             ?      593           
  Lines             ?    78207           
  Branches          ?        0           
=========================================
  Hits              ?    33028           
  Misses            ?    41128           
  Partials          ?     4051

Impacted Files	Coverage Δ
modules/setting/git.go	65.38% <ø> (ø)
cmd/hook.go	0% <0%> (ø)

---

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 7b62e9a...3fe901b. Read the comment docs.

[zeripath]

We should expect to have to fix several NPEs in the coming weeks regarding this - however, I still think this is worthwhile.

We can also begin the process of removing all of the unnecessary loadOwner calls that this will free us from making.