Be more careful in handling unconfigured programs in the program database (backport #9967)

[mergify]

This PR contains several commits that address problems with how we were handling unconfigured programs in the program database:

• We should configure unconfigured programs before serialising them (using the Binary ProgramDb instance) in
  Distribution.Client.ProjectPlanning.configureCompiler, as otherwise we can accidentally discard information.
  Not doing so can lead to situations in which we can build a package just fine, but if we re-start a build we will fail,
  because the program database on disk stored after configuring doesn't match the program database in memory.
• As a follow-on from the above, configureRequiredProgram needs to gracefully handle an already-configured program.
  Not doing so means we would fall back to the simpleProgram treatment, which can cause Cabal to fail to configure a program such as hsc2hs which has custom logic for parsing its version number.
• When compiling a Setup executable, we would pass a program database for use of the stripExe command. However,
  the strip program might not be configured in this program database; so we make sure to configure it (in the correct
  environment).

Template Α: This PR modifies behaviour or interface.

TODO:

• 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.
• Tests have been added.

  ---

  This is an automatic backport of pull request Be more careful in handling unconfigured programs in the program database #9967 done by Mergify.

[mergify]

Cherry-pick of 8bdda9c has failed:

On branch mergify/bp/3.12/pr-9967
Your branch is up to date with 'origin/3.12'.

You are currently cherry-picking commit 8bdda9c0b.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   cabal-install/src/Distribution/Client/ProjectPlanning.hs

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   cabal-testsuite/PackageTests/ExtraProgPath/setup.out

Cherry-pick of 0a0cc19 has failed:

On branch mergify/bp/3.12/pr-9967
Your branch is ahead of 'origin/3.12' by 2 commits.
  (use "git push" to publish your local commits)

You are currently cherry-picking commit 0a0cc19f1.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   cabal-install/src/Distribution/Client/SetupWrapper.hs

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[geekosaur]

Turns out there's an API change that also breaks the build.