Rebuild postgresql for glibc upgrade

[tsndqst]

Due to the glibc update a few days ago Postgresql needs to be rebuilt.
The following warning is shown when connecting to postgres after upgrading glibc.

WARNING:  database "postgres" has a collation version mismatch
DETAIL:  The database was created using collation version 2.36, but the operating system provides version 2.38.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

Since there is a new patch release for Postgresql available I decided to bump the version too. If we just want to rebuild the existing versions I can change the template to continue using the current versions.

UPDATE: I installed the package created by this PR but the warning above didn't change. I ended up running ALTER DATABASE postgres REFRESH COLLATION VERSION to resolve the warning.

Testing the changes

• I tested the changes in this PR: YES

[tsndqst]

Looks like it is a problem with the perl package. The postgresql configure script hides the reason perl.h can't be used. I tested a couple other packages (ImageMagick and hexchat) that also compile against perl and they showed the issue more clearly.

/usr/lib/perl5/core_perl/CORE/reentr.h:124:16: fatal error: crypt.h: No such file or directory

[tsndqst]

@Chocimier what do you think about this PR and the glibc/collation warning?

[Chocimier]

IIUC the https://www.postgresql.org/docs/current/sql-altercollation.html, data in tables need to be refreshed to match the updated glibc.
The right library version mentioned in warning would be glibc 2.36. Using it to build our postgres is not an option. So we cannot fix issue centrally.

Thanks for reporting anyway.

[Chocimier]

Updated in #48022