When a Puppet DR is performed upgrades using PEADM fail

[davidsandilands]

Describe the Bug

When a Puppet DR is performed upgrades using PEADM fail

The configuration in /etc/puppetlabs/enterprise/conf.d on the Primary and Replica database nodes doesn't get updated after a DR promotion (because puppet infra promote replica doesn't have any knowledge of database nodes or logic for updating them).
It's all fine until an upgrade, when puppet-enterprise-installer references pe.conf and then attempts to use a Primary that no longer exists or is no longer the primary. (https://perforce.slack.com/archives/C049ZRMGU3B/p1675355140196649)
Easiest fix would probably be to make sure peadm::upgrade writes out or otherwise syncs config in enterprise/conf.d before running the installer.

Expected Behavior

The DR promotion should have no effect on the upgrade process

Steps to Reproduce

1. Follow the steps to promote the repical in a Puppet DR setup
2. Try to upgrade the cluster

Environment

ALL

Additional Context

Add any other context about the problem here.