Clarify where docs fixes can be backported

The status key for branches has lists of changes that can go in, and the lists look exclusive:

feature:

• new features, bugfixes, and security fixes are accepted.

prerelease:

• feature fixes, bugfixes, and security fixes are accepted for the upcoming feature release.

bugfix:

• bugfixes and security fixes are accepted, new binaries are still released. (Also called maintenance mode or stable release)

security:

• only security fixes are accepted and no more binaries are released, but new source-only versions can be released

end-of-life:

• release cycle is frozen; no further changes can be pushed to it.

This makes it a bit awkward to backport docs changes, especially now that the lists are included in the tag descriptions.

AFAIK, docs fixes don't need RM approval in feature, prerelease and bugfix branches. (Security branches are locked so any change needs the RM in the loop.)
Is that right, @pablogsal @Yhg1s ?

Commencez par la clé d’état liée dans Python Developer’s Guide et comparez les descriptions de ses branches avec la question docs-backport formulée. Confirmez auprès des maintainers concernés les règles d’approbation applicables aux corrections de documentation sur les branches feature, prerelease, bugfix et security ; le travail est terminé lorsque la page indique clairement vers quelles branches les modifications de documentation peuvent être backportées et si l’approbation de RM est requise.