PD check: do not treat library names as package names (backport #9132)

[mergify]

This is an automatic backport of pull request #9132 done by Mergify.
Cherry-pick of 4aa5f88 has failed:

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

You are currently cherry-picking commit 4aa5f8861.
  (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:
	new file:   cabal-testsuite/PackageTests/Regression/T9122/p/p.cabal
	new file:   cabal-testsuite/PackageTests/Regression/T9122/q/q.cabal
	new file:   cabal-testsuite/PackageTests/Regression/T9122/setup.cabal.out
	new file:   cabal-testsuite/PackageTests/Regression/T9122/setup.out
	new file:   cabal-testsuite/PackageTests/Regression/T9122/setup.test.hs
	new file:   changelog.d/issue-9122

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   Cabal/src/Distribution/PackageDescription/Check.hs

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

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[Mikolaj]

@fgaz: I think this backport request that you initiated did not go through. Is it fine to ignore so that the PR get published only in cabal 3.12? If so, could you close this PR?

[fgaz]

@Mikolaj let's get this in 3.10.2. looks like there's a github outage right now so CI doesn't work, I'll rerun later

[Mikolaj]

Sure. It still report "branch is out-of-date", though.

[Mikolaj]

These look like genuine test failures now, right? A dot missing somewhere?

[Kleidukos]

@fgaz great, you can merge manually