For sharded deployments with TLS cluster sometimes goes into "maintenance" mode with "enabling TLS" message

## Steps to reproduce

All steps to reproduce are not clear, however these steps were performed when issue was discovered

1. Deploy sharded cluster on LXD + Juju 3.1.7
2. Deploy self-signed-certificates operator
3. Integrate all shards and config server with self-signed-certificates operator
4. Remove relation between self-signed-certificates and all shards and config server
5. Integrate all shards and config server with self-signed-certificates operator for the second time.

Note:
You can adjust juju update-status hook time to speedup reproducibility with
juju model-config update-status-hook-interval=10s

## Expected behavior
Once TLS is enabled, if the certificate did not expired cluster should not re-enable TLS once it is enabled

## Actual behavior

## Versions

Operating system:

Juju CLI:

Juju agent: 3.1.7

Charm revision:

LXD:

## Log output

Juju debug log:

## Additional context

[juju.log](https://github.com/canonical/mongodb-operator/files/14651130/juju.log)

No source file, test, or entry point is named. Start by reviewing the attached juju.log and reproducing the sharded deployment with LXD, Juju 3.1.7, and self-signed-certificates using the listed relation steps. Done means an already-enabled TLS cluster does not re-enter maintenance mode or report "enabling TLS" when the relation is recreated.

Written by the indexing model from the issue text.