Update app-runtime-interfaces buildpacks approvers

[brayanhenao]

Changes

Removal of Ryan Moran

I removed Ryan Moran from all relevant groups, he is no longer part of the Buildpacks Team.

Addition of Brayan Henao, Replacing Ryan Moran in Approvers' Roles

In response to approvers responsibilities left by Ryan Moran's departure, I have taken the initiative to introduce me into some specific teams. This decision is based on the need for at least three approvers in teams where Ryan's absence created a gap. The following exceptions apply:

• Buildpacks Tooling: Given my active involvement in the v2b release process, particularly within the buildpacks-ci repository and its related counterparts, I am confident in fulfilling the approver role.

• Buildpacks Docs: I haven't taken up the approver role there yet because I haven't contributed enough to the repositories

For your reference, please review my contributions in the following areas:

• Go: Go Contributions
• Nodejs: Nodejs Contributions
• Ruby: Ruby Contributions
• Tooling: Tooling Contributions

[brayanhenao]

I'll tag some approvers from each team:

• Go: @ForestEckhardt @robdimsdale
• Nodejs: @thitch97 @TisVictress
• Ruby: @sophiewigmore @robdimsdale
• Tooling: @ForestEckhardt @sophiewigmore @robdimsdale

[brayanhenao]

C.C @Gerg

[Gerg]

Per the role revocation policy, @ryanmoran has two weeks to refute this revocation, if they wish.

[Gerg]

As for @brayanhenao's promotions: According to the promotion process, a single approval per area is sufficient in these cases because the areas have fewer than 4 approvers each.

[beyhan]

Hi @brayanhenao and @Gerg,
should Ryan be removed from the contributors.yml also? If we know that Ryan won't be active in the CF organization we do this to keep the list with the org members clean.

[brayanhenao]

@beyhan I submitted another commit modifying contributors.yml. He will not be active in the CF community

[beyhan]

The two week period is over and there was no objection. This could be merged. @Gerg