WIP: Harmonize branch protection rules

[mberz]

Repository rules

We would like harmonize repository rules across repositories.

First step is to agree on a set of rules:
https://github.com/organizations/pyfar/settings/rules

Strongly suggested based on current rules (see below)

• Restrict deletions
• Require a PR before merging
  • require 2 reviews
• Require workflows to pass before merge
  • Require up to date with base branch
  • Block force pushes

Additionally suggested

• Require linear history
• Require approval most recent push

Additional considerations

• Define rules to specify which repos and branches are to be affected.

Branch protection rules

pyfar

• Require PR to merge
  • require 2 reviews
• Require status checks to pass
• Allow force pushes by everyone

spharpy

• Require PR to merge
  • require 1 review
• Require status checks to pass
  • require branches to be up to date
• Allow force pushes by everyone

pyrato

• Require PR to merge
  • require 2 reviews
• Allow force pushes by everyone

[mberz]

I've implemented the proposed rules for all branch names matching the following patterns:
"main", "develop", "release*", "development", "master"

The workflow check rule seems to be a bit finicky in the organization wide configuration. I've kept the respective checks in the individual settings until this is configured globally.