pgsql: Don't use abort(3) in libpq's fe-print.c.

Don't use abort(3) in libpq's fe-print.c.

Causing a core dump on out-of-memory seems pretty unfriendly,
and surely is far outside the expected behavior of a general-purpose
library.  Just print an error message (as we did already) and return.
These functions unfortunately don't have an error return convention,
but code using them is probably just looking for a quick-n-dirty
print method and wouldn't bother to check anyway.

Although these functions are semi-deprecated, it still seems
appropriate to back-patch this.  In passing, also back-patch
b90e6cef1, just to reduce cosmetic differences between the
branches.

Discussion: https://postgr.es/m/3122443.1624735363@sss.pgh.pa.us

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/cf1f545bf281d3dcb7b44e6b7f21a9369024fbf0

Modified Files
--------------
src/interfaces/libpq/fe-print.c | 81 ++++++++++++++++++++++++-----------------
1 file changed, 47 insertions(+), 34 deletions(-)