Since Debian 11 was added to this module, the package name was wrong. It
was set to python-psycopg2, but the correct name is python3-psycopg2.

There's a longer analysis about this bug in https://github.com/puppetlabs/puppetlabs-postgresql/pull/1638/files#r2390588710

tl;dr:

* Debian 10 used python-psycopg2 and that was set by the module
* Debian 11 was added without proper acceptance testing
* Later on unit tests were added for Debian 11, but still with the wrong
  package name
* 651c2b4 fixed the package name, but
  in the wrong place and didn't adjust the tests
* That resulted in a broken pipeline, that's how I found all of this

This patch:
* Cleans up the hiera data
* sets the package name at the correct location
* adjusts the debian 11 unit test for the new package name
* Adds tests for Debian 12 and 13 (won't be executed right now because
  Perforce ships a too old version of FacterDB)

Edit: Had to remove Debian 13 because the pipeline fails if it cannot
find a factset.

Debian 11: Use correct package name for python bindings

Release prep v10.6.0

Type aliases from modules aren't available on the agent.
See https://puppet.atlassian.net/browse/PUP-7197

This means that calls to `postgresql::postgresql_password` can't be
deferred if the `hash` parameter uses the type
`Postgresql::Pg_password_encryption`. Instead we have to use the raw
`Enum`, (which unfortunately causes code duplication, but this is
unavoidable).

Using this function with `Deferred` is not just a theoretical use-case.
The module itself tries to here.
https://github.com/puppetlabs/puppetlabs-postgresql/blob/20704ffae24dcf970784697b1798c09d026fb7f8/manifests/server/role.pp#L162

Don't use type alias in `postgresql_password` parameter