"Cross-link" PEP 725 and name mappings PEP

[jaimergp]

Currently we have PEP 725 and the upcoming "name mapping PEP" (number to be assigned). We decided to submit these separately instead of merging them in a single document, but they should refer to each other as necessary. Right now, only the mappings PEP refers to PEP 725, but PEP 725 only speaks of "future PEPs" in a generic way.

We need to:

• Review name mapping PEP to address latest feedback
  • Review name mapping PEP #39
  • Name mapping PEP: Security Implications #40
  • Name mapping PEP: Governance #41
  • Name mapping PEP: More rejected Ideas #43
  • Re-introduce query commands with a new package_managers.commands schema #44
  • Add Michal as co-author, update date #46
  • Name mapping PEP: Another general review #51
  • Describe specifier_syntax #50
  • Name mapping PEP: Minor editorial changes #56
  • Remove mermaid extension #57
  • Add Requires field #58
• Submit the name mapping PEP as a draft: PEP 804: An external dependency registry and name mapping mechanism python/peps#4572
• Update PEP 725 to refer to the name mapping PEP explicitly, with its number (PEP 725: reference PEP 804 #59)
• Re-submit PEP 725 (PEP 725: version 3, address all feedback and open issues python/peps#4573)

[jaimergp]

Looks like the name mapping PEP will probably have a 80x number:

$ uvx pepotron next
Next available PEP: 804

[rgommers]

Update PEP 725 to refer to the name mapping PEP explicitly, with its number

I used PEP 700 as the placeholder reference for now; once the new PEP has a number, it can be updated to that.

[jaimergp]

Submitted as 804: python#4572

[rgommers]

PEP 725 update PR opened: python#4573.

All set here, closing.