Add a new section named development in issue view sidebar to interact with branch/pr

[lunny]

Partially Resolve #20226

This PR add a new section on the sidebar of issue named Development. It supports creating one or multiple branches and pull requests from the sidebar.

1. No related branch or PR
   

2. Create new branch from the issue

3. Related branch created

4. Prefill title and content when creating pull request from the issue development link
   

5. Realted PR created
   

6. Related PR merged
   

7. Mayge fixed near the issue title
   

• Delete dev_link records from the database when deleting repos/issues
• Delete dev_link records from the database when deleting pull requests/branch
• Allow creating multiple branches/pull requests from UI
• Bring issue information into the pull request when creating the pull request.
• Adjust the toast z-index to 9999 so that it will display in front of the modal.

[lunny]

I think this is ready to review again.

[wxiaoguang]

Why GitHub-only ? Agit PR can't be used to close an issue?

[lunny]

Agit PR have no real head branch. So that branch, err := git_model.GetBranch(ctx, pr.HeadRepoID, pr.HeadBranch) will fail.

[wxiaoguang]

Is it really reasonable?

Here you are creating "IssueDevLinkTypePullRequest" dev-links.

You mean that AGit PR can't be used to link to an issue and close the related issue?

[wxiaoguang]

Please don't use the data from root template data.

Most side bar parts have been refactored to use their own "struct" types to make code stable.

[wxiaoguang]

I think this is ready to review again.

I don't.

• https://github.com/go-gitea/gitea/pull/31899/files#r1881918670

[bircni]

@lunny updates on that?

[lunny]

@lunny updates on that?

Updated.

[wxiaoguang]

https://github.com/go-gitea/gitea/pull/31899/files#r1881918670

[claesrosell]

I just downloaded this branch to play around with the development sidebar in its current state, to test the edge cases that wxiaoguang mentioned earlier.

The rename and delete branch scenarios behave very differently from the described GitHub behavior. This is not necessarily a bad thing, though:

1. Create a new branch (123-my-issue) and rename it (123-my-issue-other): The link still works, pointing to the same branch with its new name. If you delete the branch, the link disappears. If a new branch with the same name is created, the link will not magically appear again. Personally I think this behavior is better then GitHub

2. Create a new branch (123-my-issue) and create a PR from that branch: The PR shows up in the development sidebar, but the branch (with a "create PR" button) is still there. This branch should probably be hidden when a PR for it is visible in the sidebar.