Render project configs as clean list in provenance message

[philderbeast]

Fixes #9971.

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
• The documentation has been updated, if necessary.
• Manual QA notes have been included.
• Tests have been added.

[philderbeast]

@Mikolaj and @ffaf1 I saw the pre-release announcement for cabal-install-3.12.0.0. Is there still time to get this bug fix in to the release proper?

[ffaf1]

@ulysses4ever is the release manager for 3.12.1.0, which will be cabal-install proper, he will know for sure!

[Mikolaj]

LGTM

This has the potential of introducing new bugs, though, and it didn't get into the (first and last) pre-release. This is a fix for a long standing bug, not a regression, right?

[philderbeast]

This was for a situation we did not have a test for and missed at review. It is a message formatting boo-boo introduced by #9578 so its scope is limited to the display of a message.

[ulysses4ever]

For 3.12.1.0 — I'd hope so. For the prerelease — I doubt it, but @Mikolaj is managing the prerelease, I think, so he's the right person to ask.

[Mikolaj]

OK, in that case, let's get this merged soon.

The prerelease has been shipped already, BTW. Just announced. :)

[ulysses4ever]

This looks good to me, thanks! Let's apply the labels soon!

[ulysses4ever]

@philderbeast do you want to apply the merge label?

[philderbeast]

Label merge+no rebase is necessary when the pull request is from an organisation.

[Mikolaj]

@philderbeast: would you mind also rebasing manually so that the commit history is less non-linear? Thank you!

[Mikolaj]

Let me restart https://github.com/haskell/cabal/actions/runs/9080567805/job/25091173936?pr=9985. It may or may not be transient.