Document community organisation process and contacts

### Description

Eiffel Community is an active community and there are times certain requests require to be handled. Some of the example requests are
- adding/inviting people to Eiffel GitHub Organisation
- creating new repositories
- creating new maintainers group
- adjusting permissions of individuals on certain repositories

These requests are currently taken care of by few volunteers from the community. It is important the community contributes to managing Eiffel Organisation so the workload on individuals who are currently working with community support can be reduced.

In order for this to happen, it is important to
- list and document types of activities that are currently being handled by volunteers from the community
- determine the approval requirements (eg. approval of 1 TC members is sufficient for a change to pass for infra changes)
- appoint individuals as Eiffel organisation contacts

### Motivation

Identify and document community support process and contacts who look after support issues.

### Exemplification

Communities generally have list of interested/appointed people looking after support issues which Eiffel Community could adapt as well.

### Benefits

Increased visibility on how community support works and reduced workload on the current volunteers.

### Possible Drawbacks

N/A

No file or entry point is named. Start by locating the repository's existing community governance and contribution guidance, then map the volunteer-handled activities and approval requirements described in the issue. Done means the process, approval rules, and organisation contacts are documented.

Written by the indexing model from the issue text.