Managing postgresql::server::role fails when using non-default port

Describe the Bug

Before #1498, only one configuration key was needed to manage both postgresql::server and postgresql::server::role: postgresql::server::port.

Since the PR, if only the first key is set, Puppet will fail to create the role claiming it can't connect to port 5432.
We are now forced to set 2 configuration keys when we want to start postgresql server on a custom TCP port:

---
postgresql::server::port: 5433
postgresql::globals::default_connect_settings:
  "PGPORT": "5433"

Expected Behavior

One key to manage tcp port for both server and managed resources (role, extension, ...).

Steps to Reproduce

Steps to reproduce the behavior:

1. Set postgresql::server with a custom port (eg 5433)
2. Set postgresql::server::role
3. Do a puppet run and see postgresql::server::role failing

Environment

• puppetlabs-postgresql 10.0.2
• Platform - RHEL9/Postgresql 16

Start by reproducing the Puppet run with postgresql::server::port set to 5433 and postgresql::server::role managed without PGPORT. Trace how the server port and default_connect_settings reach the role connection. Done means the role and other managed resources use the configured custom port without requiring a second setting.