"maintain" cannot be used to verify actor permissions

### Describe the Issue

The "maintain" permission cannot be used to to verify the actor permissions. As a user with the "maintain" permission I would expect the following configuration to work. However, a comment is created that I only have the "write" permission.

Reading the GH API docs, it clearly states the "permission" field uses legacy base roles and that "maintain" is mapped to "write" [(ref)](https://docs.github.com/en/rest/collaborators/collaborators?apiVersion=2026-03-10#get-repository-permissions-for-a-user). So the output is expected but it is not clearly stated in this Action's documentation. Furthermore, using this legacy permission field of the API prevents us from differentiating between users with the write and users with the maintain role. In our case, we only want maintainers to be able to use the defined command and not developers with the "write" role.

### Action Configuration

```yaml
steps:
- uses: github/command@v2
id: command
with:
command: "/tf-apply"
permissions: maintain,admin
allowed_contexts: pull_request
reaction: "rocket"
skip_ci: true
```

### Relevant Actions Log Output

```
👋 , seems as if you have not maintain/admin permissions in this repo, permissions: write
```

### Extra Information

_No response_

Inizia con la configurazione github/command@v2 fornita e con il controllo delle autorizzazioni che produce l’output del log mostrato. Confronta il campo delle autorizzazioni della GitHub API con i ruoli maintain e write, quindi verifica il comportamento usando la configurazione del workflow fornita. Il lavoro è completo quando gli utenti con il ruolo maintain possono essere distinti dagli utenti con il ruolo write, oppure quando il limite è documentato chiaramente se l’API non supporta questa distinzione.

Scritto dal modello di indicizzazione a partire dal testo della issue.