postgresql::server::config_entry - dependency cycles detected (after upgrade to 10.0.0)

Describe the Bug

After upgrade from 9.2.0 to 10.0.0 or 10.0.1 puppet fails with dependency cycle error:
Error: Found 1 dependency cycle: (Anchor[postgresql::server::service::begin::main] => Postgresql_psql[Set template1 encoding to UTF8] => Postgresql::Server::Instance::Late_initdb[main] => Postgresql::Server::Instance::Initdb[main] => Class[Postgresql::Server::Initdb] => Postgresql_conf[wal_level] => Class[Postgresql::Server::Service] => Postgresql::Server::Instance::Service[main] => Anchor[postgresql::server::service::begin::main])\nCycle graph written to /opt/puppetlabs/puppet/cache/state/graphs/cycles.dot. Error: Failed to apply catalog: One or more resource dependency cycles detected in graph

Expected Behavior

Update the config entry to postgresql.conf

Steps to Reproduce

Steps to reproduce the behavior:

For example change the wal_level

postgresql::server::config_entry { 'wal_level':
value => 'archive',
}

Apply puppet and it fails.

Environment

• Version [Puppet 7]
• Platform [Ubuntu 20.04]
• Postgresql-14
• puppetlab-postgresql (since 10.0.0)

Start by reproducing the dependency cycle with postgresql::server::config_entry for wal_level on the stated Puppet, Ubuntu, and PostgreSQL versions, then inspect the generated cycles.dot graph. Done means the wal_level entry updates postgresql.conf and the catalog applies without a dependency cycle.