gh-131372: Configurable build-details.json name

[stefanor]

Linux distributions that co-install multiple Python versions in the same path (e.g. multiarch on Debian, debug builds, and free-threading) need a way to place multiple build-details.jsons side-by-side.

PEP-739 is being updated to recommend renaming in this situation. To ensure some standardisation, this PR generates appropriate names for distributions that need to use this feature. The name will be exposed in sysconfig.

My first preference would be to always do this, using the ABIFLAGS directly in the name. But this leads to less-human-readable names and the PEP authors preferred a static name where possible and a more verbose name, when we choose to rename.

@FFY00

• Issue: build-details.json should be installed to different locations for nondebug/debug builds and have distinct base_interpreter values #131372

[FFY00]

I would prefer to rename the configure option to something like --with-build-details-identifier, working similarly to --with-build-python. If the option wasn't passed, no identifier is added, if it is passed without value, it would default to $MULTIARCH$threading_suffix$debug_suffix, and if it is passed with a value, the specified value would be used.

What do you think?

[stefanor]

That works for me!

[stefanor]

@FFY00: Implemented that

[picnixz]

Can we have an issue for those kind of changes? this is solely so that people can more easily report issues later and for cross-references (or use an existing one)

[stefanor]

Can we have an issue for those kind of changes? this is solely so that people can more easily report issues later and for cross-references (or use an existing one)

Ah, there was already an issue, I'd forgotten about it.