Allow force push to protected branches

[henrygoodman]

Fixes #22722

Problem

Currently, it is not possible to force push to a branch with branch protection rules in place. There are often times where this is necessary (CI workflows/administrative tasks etc).

The current workaround is to rename/remove the branch protection, perform the force push, and then reinstate the protections.

Solution

Provide an additional section in the branch protection rules to allow users to specify which users with push access can also force push to the branch. The default value of the rule will be set to Disabled, and the UI is intuitive and very similar to the Push section.

It is worth noting in this implementation that allowing force push does not override regular push access, and both will need to be enabled for a user to force push.

This applies to manual force push to a remote, and also in Gitea UI updating a PR by rebase (which requires force push)

This modifies the BranchProtection API structs to add:

• enable_force_push bool
• enable_force_push_whitelist bool
• force_push_whitelist_usernames string[]
• force_push_whitelist_teams string[]
• force_push_whitelist_deploy_keys bool

Updated Branch Protection UI:

Pull Request Update branch by Rebase option enabled with source branch test being a protected branch:

[henrygoodman]

Will be able to fix CI compliance Sunday night

[henrygoodman]

Small refactor in commit f28ecbe seemed necessary due to make lint showing duplicated code error, despite the 2 functions in question being quite distinct. I don't think my implementation is particularly elegant, but the almighty linter must be appeased😢

[Nova-Logic]

this is very needed feature for our git workflow

[lunny]

Please fix the lint error

wait for more "naming" changes.

[phild5]

I'm running 1.22.0 and i'm looking all over the place for this. Where and how do i enable it? Doesn't show up on my branch protection screen.

[henrygoodman]

I'm running 1.22.0 and i'm looking all over the place for this. Where and how do i enable it? Doesn't show up on my branch protection screen.

This is not integrated as part of 1.22.0, it is on the roadmap for 1.23.0 (might have to look around for an ETA). If you switch to nightly build it will also have changes based on current main branch, but it is not as stable as official releases