Add openssl support for postgresql (in order to support secure replication)

(cherry picked from commit 23f41cfe37d40dca2c104633f5d55737deb827ec)
Rewrite autobuild references to buildscripts after project rename.

(cherry picked from commit 24529fb4ec9cd7d08e4c2ee272b15b227c652e6c)
Revert "lcov upgrade"

This reverts commit c788280f8a6e09913484853ba5f9d4de6efa516a.

The source file is not available on any mirror I can find.

(cherry picked from commit e18ea6aa771e39f844ceb2fc39205ba9757b5c4c)
Update a whole bunch of download sources that have gone stale.

Additionally, try to stick to plain HTTP, since some in-house
platforms have wget installed without HTTPS and FTP support.

(cherry picked from commit 5756ae4fc28e47a0edeb2fb184d49a2d269e080b)
Ignore errors because we don't have an SSL certificate.

We will catch errors using the MD5 sum anyway.

(cherry picked from commit 45211a181026b1052d9300ae1ecf2d28cfe9d905)
Change source link to pcre.

It is still available at the old source, but the mirror is unstable.

(cherry picked from commit 7bb0f033cd35f02e5c61e56691c99fc5d9eee0c7)
move the key generation process , just before sources files get deployed to their location by post install script.
(cherry picked from commit fb1038b8aff9c5671da13c526a3a9a6660f4a257)
escape any postgres initialisation process if there is postgres data directory , as if it exist we know we already have the cfengines postgres on the machine. fix for #5843
(cherry picked from commit 410ad5996e404c93d680eb7dca1fb46a0dd7b1fc)
carrying out all the initialisation task on first install of the package, so it would not trigger  undesired affect like wiping out users data on upgrade install as described in #6449
, also the right approach would be to remove those drop statements from the sql files in mp repo.
(cherry picked from commit 19a50f646567cfc5aebf220c148b3372f707dbd7)