Closed previous PR and created new one to rebase branch on Foundation-2022: https://github.com/OpenNMS/opennms/pull/5163

PR: https://github.com/OpenNMS/opennms/pull/5146

I've installed now an Ubuntu 22.04 server and PostgreSQL 14.

As you can see the default is here SCRAM:

```

postgres@ubuntuserver2204:/root$ cat /etc/postgresql/14/main/pg_hba.conf  | grep -v ^#

local   all             postgres                                peer

local   all             all                                     peer
host    all             all             127.0.0.1/32            scram-sha-256
host    all             all             ::1/128                 scram-sha-256
local   replication     all                                     peer
host    replication     all             127.0.0.1/32            scram-sha-256
host    replication     all             ::1/128                 scram-sha-256
```
```
postgres@ubuntuserver2204:/root$ cat /etc/postgresql/14/main/postgresql.conf | grep scram
#password_encryption = scram-sha-256    # scram-sha-256 or md5
```

By following the normal installation process we have everything working fine. So I guess we could just add a hint to change to consider using SCRAM when running PG < 14.

With PG 14 the default changed to SCRAM as you can see here:
https://www.postgresql.org/docs/14/runtime-config-connection.html#GUC-PASSWORD-ENCRYPTION (The default is scram-sha-256.)

Here for PG 13:
https://www.postgresql.org/docs/13/runtime-config-connection.html#GUC-PASSWORD-ENCRYPTION (The default value is md5)

As long as we don't require to use PG 14 (and our call yesterday identified that CentOS 7 is still using PG 10) for ONMS, we should probably just add a hint in our PG installation docs that MD5 should not be used anymore.
But of course we should test first if ONMS is working using SCRAM. I will give that a try.

FYI

The JDBC upgrade is not required to use SCRAM, but an additional step to bring this PG Jdbc topics up to date.