Update cf-credhub team membership

[peterhaochen47]

• removes past members
• adds new member Tallicia, who just joined our team

[stephanme]

Credhub is part of the FI working group. Approvers should be maintained directly in the yaml block of the WG charter (https://github.com/cloudfoundry/community/blob/main/toc/working-groups/foundational-infrastructure.md).
The following github team is generated from the WG charter for Credhub: https://github.com/orgs/cloudfoundry/teams/wg-foundational-infrastructure-credential-management-credhub-approvers
Manually maintained (aka non-standard) github teams will be deleted by #262 .

[peterhaochen47]

Credhub is part of the FI working group. Approvers should be maintained directly in the yaml block of the WG charter (https://github.com/cloudfoundry/community/blob/main/toc/working-groups/foundational-infrastructure.md). The following github team is generated from the WG charter for Credhub: https://github.com/orgs/cloudfoundry/teams/wg-foundational-infrastructure-credential-management-credhub-approvers Manually maintained (aka non-standard) github teams will be deleted by #262 .

@stephanme Thank you for the information. This PR is only about adjusting the members section of credhub team, not maintainers / Approvers.

For this PR, I am following this instruction:

A Working Group approver or lead should raise a PR on the community repository to propose adding a new member to the cloudfoundry GitHub org. This PR should add the member directly to the YAML file describing the organization membership, as automation will synchronize the GitHub org membership with the contents of this file periodically.

Is this PR not the right way to "propose adding a new member to the cloudfoundry GitHub org?"

[emalm]

Hey, @peterhaochen47 , now that #262 is accepted as RFC 0013, #387 will remove all the teams that aren't derived from official Working Group and TOC roles, so the change in this PR wouldn't persist for long.

I think what you want to do instead is to follow the process at https://github.com/cloudfoundry/community/blob/main/toc/ROLES.md#promotion-to-contributor to add @Tallicia as a Contributor in the CF org. That process includes getting them them to the separate list of contributors -- the specifics of RFC 0002 are a little out of date, since we extracted the organization member list from the cloudfoundry.yml file into that separate contributors file after it was accepted. As a Contributor, they can then contribute towards becoming a Reviewer and then an Approver in the CredHub area.

[peterhaochen47]

@emalm Makes sense. We will start using the new process. Closing this PR.