Allow mage-os-ci user to push to remote bypassing branch protections about terraform

[sprankhub]

I wondered that you talk about push_allowances, because we used push_restrictions until now. Turned out we need a Terraform update, which I executed in #86.

Your suggestions sound good to me. I'd personally say we can go with the slightly "less secure" option 2. However, I don't feel comfortable deciding this alone. Hence, I'm dragging in the @mage-os/infrastructure team, @Vinai @damienwebdev @DavidLambauer.

[sprankhub]

@Vinai, @damienwebdev, @DavidLambauer, could someone share their opinion on this one?

[damienwebdev]

I don't have enough familiarity with this to comment.

[furan917]

If you wouldn't mind a random flyby, I would strongly recommend that option 2 not be taken lightly.

It would be better to be as explicit as possible. Id suggest either by allowing for a new item within your objects or a user to repo map that is considered during branch rule/branch protection setup. This way you dont have issues aligning global changes, and your user doesnt get additional privelages in much more repos than necessary.

[DavidLambauer]

We can loosen the permissions, as it would also benefit me in the DevDocs repository. Permissions should be managed at the user level.

[Vinai]

I think keeping the setup more secure by default is the way to go.