pgsql: Cope with cross-compiling when checking for a random-number sour

Cope with cross-compiling when checking for a random-number source.

Commit 16f96c74d neglected to consider the possibility of cross-compiling,
causing cross-compiles to fail at the configure stage unless you'd
selected --with-openssl. Since we're now more or less assuming that
/dev/urandom is available everywhere, it seems reasonable to assume
that the cross-compile target has it too, rather than failing.

Per complaint from Vincas Dargis. Back-patch to v14 where this came in.

Discussion: /messages/by-id/0dc14a31-acaf-8cae-0df4-a87339b22bd9@gmail.com

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/175edafd1f30a78643359b56c5545b5e7aabfb50

Modified Files
--------------
configure | 5 ++++-
configure.ac | 4 +++-
2 files changed, 7 insertions(+), 2 deletions(-)