Adding an explicit pgmcxx flag for interaction with GHC

[zlonast]

Add an explicit pgmcxx flag to Cabal's GHC invocation logic. This aligns
with the existing pgmc behavior and accounts for the GHC 9.4+ toolchain
requirements, resolving inconsistencies in how C++ compiler options are handled.

This change allows users to remove extra-libraries: stdc++ from their
configuration files, as g++ automatically handles C++ standard library
linking, unlike the legacy approach of invoking C++ via gcc.

Main idea #9801 (comment)

IMHO, cc-options (and ld-options and cpp-options and ...) should be always passed when invoking GHC, similarly as ghc-options should be always used when invoking ghc - regardless of what is the intention of a particular GHC-call. GHC might use or not use the options, Cabal cannot know and should not guess.

Template Α: This PR modifies behaviour or interface

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Any changes that could be relevant to users have been recorded in the changelog.
  • Is the change significant? If so, remember to add significance: significant in the changelog file.
• The documentation has been updated, if necessary.
• Manual QA notes have been included.
• Tests have been added. (Ask for help if you don’t know how to write them! Ask for an exemption if tests are too complex for too little coverage!)

[zlonast]

This pr is a logical continuation of this #11713