Add more documentation/examples about bypass_teams option

[zabetak]

With the upcoming "Updated GitHub repository security recommendations and actions for ASF projects" and given that by default I see that the .asf.yaml snippet contains the following entry

      bypass_teams:
        - root

I would like to understand more about this option.

First of all I would like to confirm that this group can bypass the defined rulesets. In other words, are people in this group capable of force-pushing and restoring a branch to an arbitrary state?

Secondly, I would like to know what does root mean, and which people/team are part of it. If problems arise and we want to contact them to perform a force-push what's the recommended path forward.

Finally, can we have form arbitrary groups of people that have these special bypass permissions? Is it possible for instance to just have the PMC chair of the project capable of bypassing the rulesets?

[Humbedooh]

First of all I would like to confirm that this group can bypass the defined rulesets. In other words, are people in this group capable of force-pushing and restoring a branch to an arbitrary state?

Yes, that is correct. people or teams in the bypass lists can be exempt from rulesets

Secondly, I would like to know what does root mean, and which people/team are part of it. If problems arise and we want to contact them to perform a force-push what's the recommended path forward.

This is the apache/root team, aka infrastructure-root or root@apache.org.

Finally, can we have form arbitrary groups of people that have these special bypass permissions? Is it possible for instance to just have the PMC chair of the project capable of bypassing the rulesets?

Yes, anyone with existing write access to the repository can be considered for bypassing rules.
The convenience syntax only accepts the bypass_teams list, but you can do overrides for individual contributors if you use GitHub's raw payload syntax instead. See https://github.com/apache/infrastructure-asfyaml#rulesets as well as https://docs.github.com/en/rest/repos/rules?apiVersion=2022-11-28#create-a-repository-ruleset for the data required.