ORG: Committers review and approve contributions

The Eclipse S-CORE documentation introduces a notion of _technical lead_ which is not formalised in the Eclipse Foundation Development Process (EDP).

In the description of the role, it is suggested that technical leads are responsible for reviewing and approving contributions.

https://github.com/eclipse-score/score/blob/8e8891d6e5bc76a2dcc561fbefd2239b6ff1961a/docs/platform_management_plan/project_management.rst?plain=1#L52

Per the EDP, this is a responsibility for _committers_. As a minimum, anybody who is designated as having this responsibility must have committer status as that role is defined in the EDP.

It is completely reasonable to define the role, but those who hold the role only have as much authority as the project committers grant them.

Further, when you are defining a formal role, there must be a well defined open path to achieve that role. "Project leads get to appoint who they want" (paraphrasing) isn't particularly open.

e.g,.

1. Individual shows up to the vendor neutral open source Eclipse S-CORE project and starts making contributions
2. After having publicly made a significant number of high quality contributions and demonstrating that they understand the open source process, the individual is invited to join the project as a committer
3. After publicly demonstrating technical leadership by (for example) mentoring other committers, contributors, and adopters, the individual is invited to join the technical lead circle.