Print full PSIO error message to cerr as well

[TiborGY]

Description

For some poorly understood confluence of reasons, for some users error messages can sometimes get completely lost when Psi4 exits with a PSIEXCEPTION, especially when a PSIO error happens.
This can be observed in recent bug reports, see:

• v1.7 PSIO_ERROR + forrtl: error + core dumped #2970
• https://forum.psicode.org/t/sapt0-calculation-crashes-pointer-error/2839

In both of these cases the users were only seeing the error message that has been written to cerr, but not the string that PSIEXCEPTION should have printed.

IIRC when I tried to research this quite a while ago, I have found this may be a bug in some versions of libstdc++. This PR adds a simple workaround: the exception message is also printed to cerr in psio_error.

The only side effect, is that some users, who are currently not affected by the lost message problem, may start getting the same error message twice when a PSIO error happens. Spammy error exits are not great, but PSIO errors are not supposed to happen too often, and when they do loosing the error message is more annoying than having it be duplicated.

User API & Changelog headlines

• PSIO error messages are now also printed to cerr, fixing an issue where (under some circumstances) large parts of the error message would never reach the user,

Dev notes & details

• The same error message that gets passed to PSIEXCEPTION is now printed to cerr before throwing in psio_error

Checklist

• There is no easy way to add tests for "are error messages getting delivered or not?"
• Tests run by the CI are passing

Status

• Ready for review
• Ready for merge

[loriab]

I completely agree better two error messages than zero. Thanks for the fix.

Hopefully #1657 #2999 will fix the CI.

EDIT: fixed PR number

[loriab]

I'm going to update the branch and then add to merge queue, so heads-up that local != remote.