Split translating.rst into pages for Translators and Coordinators

[StanFromIreland]

I propose that the existing page be split into two pages, a page for each key audience, coordinators, and translators. This, will help keep the pages organized allowing for better expansion. That is, to facilitate content on best practices (@nedbat @irvan-putra @jwjacobson) and to provide transperency (@willingc).

---

📚 Documentation preview 📚: https://cpython-devguide--1575.org.readthedocs.build/

[willingc]

@StanFromIreland I like this approach to splitting this up in the devguide I did a quick skim of the document for coordinators, and it's looking really good. I'll do a more thorough review on the weekend. Thanks for the effort and pinging me to take a look. 💯 💐

cc/ @encukou It's cool to see this draft PR 👍🏼

[StanFromIreland]

I haven't added any new content, I have so far just split the existing text. I think it is generally preferred to not mix new text to make it easier to review, and do it in a separate pull request?

I do plan to expand both sections (starting with that for translators) right after if this is merged.

[willingc]

Thank you @StanFromIreland for this helpful improvement. If you agree with the suggested changes, I am happy to merge. Alternatively, we can iterate on those suggestions if needed.

[StanFromIreland]

Ah, your suggestions modify the existing wording, which I already have a few patches (& questions) for.

I can commit them for now since they are improvements, and we can iterate further on them in the next prs.

[willingc]

Thanks @StanFromIreland. I'm looking forward to the next PR.