Sync branches to DB immediately when handle git hook calling

[wolfogre]

Unlike other async processing in the queue, we should sync branches to the DB immediately when handling git hook calling. If it fails, users can see the error message in the output of the git command.

It can avoid potential inconsistency issues, and help #29494.

[lunny]

The first sync for a repository with many branches will wait for a long time.

[wolfogre]

The first sync for a repository with many branches will wait for a long time.

It makes sense. What about keeping the old way to sync branches but adding additional pre-sync for the default branch only?

It's not ideal, but I don't have a better idea.

---

Update:

Maybe it's not a problem, because if the user synced many branches, they have already waited for a long time for the git operations. After that, a little more time to wait for db operations may not matter.

---

Update:

I tested both the main branch and this branch by creating 1000 branches and pushing them to the remote at once.

Steps

1. Created 1000 branches

for i in $(seq 1 1000); do
  git checkout -b branch-$i main
  echo "This is branch $i" > branch-$i.txt
  git add --all
  git commit -m "Commit for branch $i"
done

2. Delete and create an empty repo on Gitea.
3. Push

time git push origin --all

Result:

	main	this PR	delta
1	137.98s	178.18s
2	135.78s	180.32s
3	136.19s	188.29s
avg	136.65s	182.26s	+33.38%

So, this PR will increase the time to push by about 30%. It's hard to say if the result is good or bad. I think this is a matter of trade-offs.

I am surprised it took so long, and I tried to push the repo to gitea.com, it also took 108.76s.

---

Update:

After 49f224a , the performance has been improved.

The new result:

	main	this PR	delta
1	137.98s	139.79s
2	135.78s	138.22s
3	136.19s	136.41s
avg	136.65s	138.14s	+1.09%

In this way, the performance impact is very limited.

[lunny]

Looks like the default branch of the repository hasn't been set correctly for the first push

[wolfogre]

Looks like the default branch of the repository hasn't been set correctly for the first push

I cannot reproduce; I believe it's unrelated.