Improvements to Lifecycle of a pull request

I write this issue as a feedback from Euro Python 2024 sprint to denote troubles I encountered as I contributed to cpython.

Describe the enhancement or feature you'd like
Missing content in "Lifecycle of a pull request" https://devguide.python.org/getting-started/pull-request-lifecycle/

• "Quick guide" is missing a step to create NEWS.d record. It's just very briefly mentioned in patchcheck.
• "Step-by-step guide" doesn't denote a branch naming convention. I was told to use gh-<number>-<name>.
• "Making good commits" doesn't mention gh-<number> should be included in the commit message.
• "Step-by-step guide" doesn't mention gh-<number> should be included in the PR title.

Describe alternatives you've considered
None.

Comienza con la página vinculada “Lifecycle of a pull request” en la guía Python developer’s guide y revisa sus secciones Quick guide, Step-by-step guide y Making good commits. Actualiza la documentación para cubrir el registro NEWS.d y las convenciones de nomenclatura y de mensajes de gh-; se considera terminado cuando los cuatro detalles del flujo de trabajo solicitados estén claramente indicados.