Test-infra: override: allow top-level OWNERS to override contexts

[stevekuznetsov]

Today the override plugin uses GitHub access control (repository admin) to determine if a user can use /override. The rest of Prow and the SIG in general wants to move away from using these access controls and having workflows that require more than read access, so we should use some other means of detecting this. For instance, we could use the top-level OWNERS files for a list of people who can /override.

/area hook
/cc @cblecker @nikhita @cjwagner @fejta

[stevekuznetsov]

/cc @tnozicka

[cblecker]

Either that, or a GitHub team (that isn't necessarily tied to permissions).

Not 100% sure which is a better approach

[stevekuznetsov]

GitHub team might be a nice option but does not scale, implicit OWNERS will be less friction.

[nikhita]

Why not both :upside_down_face:

We can have config options like allow_top_level_owners _and_ github_teams (containing info about team id and name) and the repo maintainers can decide which ones they'd like to use.

[nikhita]

And repo admins would have power to override implicitly too (existing behaviour)

[stevekuznetsov]

All three sounds good :)