Also display "recently pushed branch" alert on PR view

[Naxdy]

This commit adds the "You recently pushed to branch X" alert also to PR overview, as opposed to only the repository's home page.

GitHub also shows this alert on the PR list, as well as the home page, which makes sense, since a common flow is:

1. Go to issues page
2. Grab an issue to work on
3. Branch off
4. Work
5. Push
6. Open PR

For step 6, many devs' intuition is to go directly to the pull request page, to open a new PR. However, in current Gitea, this is actually not optimal, since this would require you to enter your PR details manually, and going to the home page would let you take a shortcut, which is unintuitive.

---

Screenshots:

PR List:

[silverwind]

But GH does not show it on the issues page right? Why should we?

[Naxdy]

My thought was mainly because of time tracking. So if you work on something, then go to stop your time tracking, you have the alert close by. I have no strong feelings towards that part however.

[silverwind]

Maybe keep it to the PR page. Issue page with issue pins visible would be quite overloaded imho.

[wxiaoguang]

Two things in my mind:

1. Please keep the function in "route" related packages
2. Please don't show the banner on the "issue list" page

[Naxdy]

Changed it to only show on the PR page due to popular demand, and also moved the file back to routers/utils.

[silverwind]

We can show it on the repo homepage though, example from GitHub:

BTW I wish there was a way to never show these messages for certain branches, like our release/v1.24 which is a release branch and not meant to be pulled into main.

[Naxdy]

We can show it on the repo homepage though, example from GitHub:

This is the current behavior, which I didn't change. Sorry if I made it seem like I removed that functionality in favor of having it only on the PR view, that's not the case! :)

[silverwind]

Ah I wasn't aware. So we show it on:

• Frontpage
• Repo Homepage
• Pull Requests List (with this PR)

Is that correct?

[Naxdy]

Yep, that covers it!

[wxiaoguang]

Thank you very much for the PR. Your change is good enough. I made some more changes, some ideas are:

• Move the code from "route/utils" package to "route/repo" package
  • By reading other code in "route/utils" package, it seems that "util" is more suitable for some functions to "help"
  • Our prepareRecentlyPushedNewBranches prepares the template rendering data, so "route/repo" seems more suitable
• Introduce repo.CanContentChange to replace IsMirror check
  • That's a more complete check for whether a repo is changeable
  • I found the problem when working on other PRs, now it seems a good chance to introduce it and make prepareRecentlyPushedNewBranches better
• Introduce a dedicated struct to pass "RecentBranchesPromptData"
  • Golang template is quite fragile, so if there is a chance, I'd like to clearly define the variable name and struct, to make it less fragile.
  • And no need to use the if PageIsPull check, now the template only renders when there is "RecentBranchesPromptData"
• Fine tune the template and simplify the tw-xx helpers
  • Related to Some "good first issues" (likely easy to fix) for contributors #35015

So I made some changes that I'd like to do sooner or later in this PR together 😆 🙏

Screenshot (no visual change):