Race condition when integrating sssd and ldap provider before integrating sssd with principal charm

If the sssd charm is integrated with an ldap provider like glauth-k8s before sssd is integrated with a principal charm like slurmd, _sssd.conf_ will not be updated with the relevant ldap server configuration information. This means that sssd will successfully start, but it won't actually bind to the ldap server like we want SSSD to.

### Possible fix

The likely fix for this issue is to "query the state of the world" after a hook execution and check if any updates to the _sssd.conf_ file are required. We already have the `refresh` hook which inspects the state of the machine and ensuring necessary integrations are present, so we could use the decorator to determine an update is required to the _sssd.conf_ file and restart SSSD.

### Additional notes

Originally reported by @jedel1043

Start with the refresh hook and its decorator, then trace how integrations update sssd.conf when LDAP and a principal charm are added in different orders. Reproduce the LDAP-first sequence and verify that the LDAP server configuration is present and SSSD is restarted after the state is reconciled.

Written by the indexing model from the issue text.